24 messages in org.oasis-open.lists.sca-jISSUE 12: Relation between conversati...| From | Sent On | Attachments |
|---|---|---|
| Simon Nash | Sep 26, 2007 6:42 am | |
| Peshev, Peter | Sep 27, 2007 8:48 am | |
| Barack, Ron | Oct 4, 2007 11:03 am | |
| Barack, Ron | Oct 4, 2007 11:07 am | |
| Peshev, Peter | Oct 4, 2007 12:03 pm | |
| Peshev, Peter | Oct 4, 2007 11:29 pm | |
| Peshev, Peter | Oct 5, 2007 1:19 am | |
| Michael Rowley | Oct 5, 2007 6:23 am | |
| Simon Nash | Jan 15, 2008 1:44 pm | |
| Peshev, Peter | Jan 16, 2008 2:22 am | |
| Mike Edwards | Jan 16, 2008 4:44 am | |
| Peshev, Peter | Jan 17, 2008 4:01 am | |
| Mike Edwards | Jan 21, 2008 9:41 am | |
| Simon Nash | Jan 31, 2008 8:56 am | |
| Mike Edwards | Feb 1, 2008 3:02 am | |
| Peshev, Peter | Feb 1, 2008 6:38 am | |
| Simon Nash | Feb 7, 2008 9:37 am | |
| Peshev, Peter | Feb 7, 2008 10:03 am | |
| Michael Rowley | Feb 7, 2008 11:33 am | |
| Mike Edwards | Feb 8, 2008 3:39 am | |
| Peshev, Peter | Feb 8, 2008 3:44 am | |
| Mike Edwards | Feb 8, 2008 3:50 am | |
| Peshev, Peter | Feb 8, 2008 4:02 am | |
| David Booz | Feb 11, 2008 1:08 pm |
| Subject: | ISSUE 12: Relation between conversational annotation and scope conversation | |
|---|---|---|
| From: | Barack, Ron (ron....@sap.com) | |
| Date: | Oct 4, 2007 11:07:18 am | |
| List: | org.oasis-open.lists.sca-j | |
http://www.osoa.org/jira/browse/JAVA-12
-----Ursprüngliche Nachricht----- Von: Peshev, Peter [mailto:pete...@sap.com] Gesendet: Donnerstag, 27. September 2007 17:48 An: sca...@lists.oasis-open.org Betreff: [sca-j] NEW ISSUE: Relation between conversational annotation and scope conversation
TARGET:
Java Common Annotations and APIs specification
DESCRIPTION:
The specification mentions @Conversational and @Scope(Conversation) but there is no clarification how these interfere together and what should happen in all the possible combinations.
PROPOSAL:
Two new paragraphs should be added in section (3.2 @Conversational) that have the following wording :
In case an interface is marked as conversational but the scope of the target implementation is different than @Scope(Conversation), than the SCA runtime would invoke an instance as defined by the scope. In case the scope is the default one (stateless) than the container may dispatch to a new instance each time or alternatively pull one from a pool. In this case, it is assumed that the implementation itself will manage state. The implementation would be responsible for using the conversation id associated with the request (obtaining it through injection or via the SCA API) to obtain state stored somewhere (cache , database , etc.).
In case the target implementation has @Scope(Conversation) and the interface is NOT marked as conversational than there will be no conversation, attempts to retrieve conversationId will result in null, and the SCA runtime may behave as if for that particular invocation the scope has been defined as stateless.