[ 
https://issues.apache.org/jira/browse/TUSCANY-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567602#action_12567602
 ] 

Thomas Greenwood commented on TUSCANY-1999:
-------------------------------------------

Thanks Simon.

It will probably be a few weeks before we get our stuff working with the latest 
Tuscany.  As long as the interfaces between the conversation manager and the 
scope container are pretty similar the fix should be OK.

> ConversationAttributes and expiry doesn't work with Stateless Conversational 
> components
> ---------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1999
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1999
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-1.1
>            Reporter: Ben Smith
>            Assignee: Simon Laws
>             Fix For: Java-SCA-Next
>
>         Attachments: ConversationExpiry.patch
>
>
> In services that are marked as @Conversational yet have scope of STATELESS 
> the following problems occur
> Caused by: 
> org.apache.tuscany.sca.implementation.java.introspect.impl.InvalidConversationalImplementation:
>  Service is marked with @ConversationAttributes but the scope is not 
> @Scope("CONVERSATION")
>       at 
> org.apache.tuscany.sca.implementation.java.introspect.impl.ConversationProcessor.visitClass(ConversationProcessor.java:57)
> Also looking at the code it looks as if that expiring of conversations only 
> occurs with services that are of scope CONVERSATION. I believe that the above 
> should work with all services marked as @Conversational. 
> To fix this I'm thinking that the job of expiring conversations should be 
> moved from the ConversationalScopeContainer into the ConversationManager and 
> the check in the ConversationProcessor changed to check for the 
> @Conversational tag not @Scope("CONVERSATION")
> Ben

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to