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

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

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


Subject: Re: [sca-bindings] Disposition of Eric's binding spec review comments



Eric,

On the topic of connection factory/activation spec, here's my analysis of the allowed combinations:

For a service:

For receiving requests:

<request>
ActivationSpec to receive requests.  For the case where resources exist, the AS also identifies the destination (as far as the runtime is concerned).
Optional Destination in the case where resources are being created, as AS doesn't provide destination attributes. if not specified when creating resources the system provides a request queue. This could also be specified so that clients can look at the export definition and know which Destination is actually being used.  In that case the Destination must be consistent with the ActivationSpec (who could check that - the SCA runtime? can't just look at the SCDL and know its wrong).
No ConnectionFactory
</request>

OR

<request>
ConnectionFactory to receive requests.
Destination to receive requests.
No ActivationSpec
</request>

For sending responses (if interface has any request/response operations):

<response>
ConnectionFactory to send responses.
Optional Destination to send responses to (if absent JMSReplyTo is used)
No ActivationSpec
</response>

No corresponding ActivationSpec case for service responses.

For a reference:

For receiving responses:

<response>
ActivationSpec to receive responses.  For the case where resources exist, the ActivationSpec also identifies the destination
Optional Destination to receive responses.  In the case where resources are being created, as ActivationSpec doesn't provide destination attributes.  If not specified when creating resources, then system provides a response queue.  There's little value in exposing the response Destination in the SCDL in the case that resources exist, but if done must be consistent with the ActivationSpec.
No ConnectionFactory
</response>

OR

<response>
ConnectionFactory to receive responses.
Optional Destination to receive responses.  If not specified, then system provides a response queue.
No ActivationSpec
</response>

For sending requests:

<request>
ConnectionFactory to send requests
Destination to send requests to
No ActivationSpec
</response>

No corresponding ActivationSpec case for reference requests.

So in summary:

If we agree with these rules then we need to make sure the text and the schema in the JMS and JCA binding specs agree with this.

Regards, Simon

Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU








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