Re: [sca-bindings] ISSUE-21: Support for callback and conversationID-s in bindings

[Eric Johnson <eric@tibco.com>]

New issue logged: http://www.osoa.org/jira/browse/BINDINGS-21

-Eric.

Peshev, Peter wrote:
> TARGET:
>
> JMS binding (may change depending on the resolution)
>
>
> DESCRIPTION:
>
> As seen on the SCA-J TC mailing list and as according to SCA-J
> specifications, there are two ids that needs to be transported by a
> binding that will be used by java components that make use of callbacks
> and conversations - conversationId and callbackId.
>  
>
> http://www.oasis-open.org/apps/org/workgroup/sca-j/email/archives/200801
> /msg00042.html
>
>
> At the moment the JMS binding has section only about the transport of
> conversationId in the JMS message. The WS binding representation says
> that conversational data is represented as "wsrm:Sequence SOAP header in
> the message" , representation of callbackId is  addressed as BINDING-2,
> the JCA binding doesn't cover at all that.
>
>
>
> PROPOSAL:
>
> Add message property with Key  scaCallbackId in the JMS binding spec,
> next to the sections that deal with scaConversationId
> (exact wording may be provided if there is need)
>
> Do nothing for binding.ws (assuming reliable messaging sequence header
> is good enough and BINDING-2 should be resolved)
>
> Do not do anything for binding.jca. IMHO runtime data format is and
> should be out of scope for it and the whole JCA.
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
>
>