On 7/19/07, Simon Laws <[EMAIL PROTECTED]> wrote:
Can anyone familiar with the conversation aspects of the spec tell me what
is the specified way to get a conversationId in a stateless service, i.e a
service which implements an @Conversational interface but is not annotated
with
@Scope("CONVERSATION").
1 Spec (1.2.5.1 of JavaComponentImplementation) says that classes that
are CONVERSATION scoped may use @ConversationID. Doesn't say that those
that
aren't conversation scoped can't
2 Ability to get component context implies
componentContext.getRequestContext
().getServiceReference().getConversation().getConversationId().
Could we get conversationId added to the request context?
I prefer 1. 2 isn't obviously what you would want to be faced with unless
we
can add more info to request context (although this way is useful if you
want to pass a reference to this conversation on to others) .
Regards
Simon
In the absence of any guidance on this how about we make @ConversationID
always actioned? Or maybe actioned unless its scope COMPOSITE in which case
it throws some exception?
...ant
