tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Laws" <simonsl...@googlemail.com>
Subject Re: [jira] Commented: (TUSCANY-1999) ConversationAttributes and expiry doesn't work with Stateless Conversational components
Date Mon, 04 Feb 2008 15:30:33 GMT
On Feb 4, 2008 12:25 PM, Thomas Greenwood (JIRA) <tuscany-dev@ws.apache.org>
wrote:

>
>    [
> https://issues.apache.org/jira/browse/TUSCANY-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565331#action_12565331]
>
> Thomas Greenwood commented on TUSCANY-1999:
> -------------------------------------------
>
> BTW I'd like the patch committed if possible since that's what we're
> currently working with.
>
> > 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: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
> Hi Thomas

I took a preliminary look at the patch and from what I've seen it looks good
so far. Had hoped to commit this straight away but I've been unwell for the
last couple of days so didn't get it done. Back on the case now so I'll go
through it again and ask questions as required.

Regards

Simon

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message