Re: [ebxml-iic] Resolution of issues during last conference call

["Monica J. Martin" <Monica.Martin@Sun.COM>]

> *- management of the message store, semantics of putting and getting 
> messages.*
>  
> [MIKE] - This was not thoroughly disccuess on the conference call due 
> to time limitation.s
> Agreed that "deletion" of messages was likley to cause side-effects in 
> a message store when
> concurrent <Thread>s are accessing the same messagestore and that an 
> optional "masking"
> of a message store ( perhaps at the <Thread> level ( i.e. having a new 
> "virtual" message store,
> local to that <Thread> whose lifecycle is the duration of that 
> <Thread>.  Incoming messages would
> go  to that <Thread>'s local message store, but would also be placed 
> in the "global" messagestore. 
> <GetMessage> operations within that <Thread> would only have access to 
> the local message
> store.  Comments?  If this is an agreeable approach, then I can update 
> the message store semantics
> in the test framework specification.

mm1: Seems like a reasonable approach to maintain integrity.

> *[MIKE] - Other issues include:*
>  
> *Global Threads -* <Thread>s defined at the <TestSuite> level.. Useful 
> for such things as
> global "exit" operations, or often used sets of <TestStep>s that vary 
> only with the
> <ConversationId> or <Timestamp> values.  I suggest adding a global 
> <ThreadGroup> at the
> <TestSuite> level to permit definition of such global <Thread>s.  
> Comments?

mm1: Sounds reasonable. May require further discussion about <Thread Group>.

>