[snip]
scabooz wrote:
Composite scoped components can have concurrent requests inflight, the
runtime does not need to serialize for concurrency.
I recall having this conversation during the spec work, but cant find
verbiage in the specs. FWIW, I recall that for composite scoped
components, we decided that it was not possible to inject
@ConversationID nor callback references, AND therefore the
component implementation would have to use the appropriate API
which would return the correct info in the context of the request.
This seems to be in line with what I'm proposing at the bottom of
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg20535.html
Some combinations are not supported, let's get this clarified in the
spec first, and when the behavior is clarified we can implement a check
in Tuscany to enforce it.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
