OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-iic-framework message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [ebxml-iic-framework] RE: TestFramework default messages 7.1. 3


Title: RE: [ebxml-iic-framework] RE: TestFramework default messages 7.1.3

Mike:

-----Original Message-----
From: Michael Kass [mailto:michael.kass@nist.gov]
Sent: Friday, January 24, 2003 11:25 AM
To: Jacques Durand
Cc: 'ebxml-iic-framework@lists.oasis-open.org'
Subject: [ebxml-iic-framework] RE: TestFramework default messages 7.1.3



>Jacques,


    I am looking further at your proposal for using the following as
<ConfigurationGroup/> parameters:  This will work, however we will have to set
"precedence rules" in our specification for their use.  I personally don't
find setting ConversationId, MessageId or Timestamp particularly useful
at the Config level.. because testing using a "globallly defined"
ConversationId, MessageId or Timestamp ( say.. for all Test Cases, or all
Test Steps)
simply does not make any sense. Besides, all can be explicitly set in the
XML PutMessage declaration. Do you agree?  If so, I would leave those three
out of the ConfigurationGroup list, and keep the rest.

<Jacques> agree with that... (but do we need in TestFramework spec
to explicitly say which parameters
can go in COnfigurationGroup / COnfigItems, and which one can't?)
So although I agree these values you mention would rather be specified
in the script putMessage dcl, it does not hurt to have the possibility to
specify them in COnfigurationItems - some future test suite may want to do this
on a test case basis, e.g. not to have to repeat a COnversationId in each test step,
or a CPA... agree that others like  that MessageId or Timestamp are uniquer to each step,
and likely to never appear in a configurationgroup.
But I am not opinionated on this... your call.
As a precedence rule, I'd say that whatever is in ConfigGroup is the default,
and will be override by anything specified in putMessage, or set by MSG...

Jacques



Comments?

Mike




Parameter Name  CPPA
Equivalent                         Precedence1     Precedence2
        Precedence3
------------------------        -------------------------
             -------------------     -------------------
  -------------------
$SenderParty            <tp:PartyInfo><tp:PartyId/></tp:PartyInfo>
CPPA            Config Param                    XML PutMessage Declaration
$ReceiverParty  <tp:PartyInfo><PartyId/></tp:PartyInfo>         CPPA
     Config Param                    XML PutMessage Declaration
$CPA
(Id)                                                               Config
Param    In XML PutMessage Declaration
$ConversationId                                                 Config
Param    Test Driver auto-generates      XML PutMessage Declaration
$Action                                                         Config
Param    In XML PutMessage Declaration
$MessageId
ConfigParam     Test Driver auto-generates      XML PutMessage Declaration
$Timestamp
Config Param    Test Driver auto-generates      XML PutMessage Declaration


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC