RE: [sca-j] Clarification: Decision regarding the Implementation of a Se

That was indeed a decision that was made at the F2F, although it hasn’t yet been figured into the specification. It believe it was an interim decision as part of the larger issue of conversation/callback simplification.

If the decision stands, then you would not be able to use a composite-scoped component to implement a conversational interface. I agree with you that that is a bit concerning and think we may want to revisit the issue.

Michael

From: Mike Edwards [mailto:mike_edwards@uk.ibm.com]
Sent: Friday, March 28, 2008 2:28 PM
To: OASIS Java
Subject: [sca-j] Clarification: Decision regarding the Implementation of a Service with a Conversational Interface

Folks,

Can anyone help clarify whether a decision has been made regarding the type of Java implementation that
is used to implement a service with a conversational interface?

In particular, has it been decided that a conversational interface MUST be implemented by a conversation
scoped component?

If this IS the case, was there any consideration of the case of a composite scoped component, which might
want to implement a conversational interface (think: in-memory database, with an interface that offers something
like a cursor that can be opened and then used in successive operations by a given client....).

Yours, Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@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

sca-j message