You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Kevin Williams (JIRA)" <tu...@ws.apache.org> on 2008/05/08 22:17:55 UTC

[jira] Created: (TUSCANY-2306) Client callback state preserved through stateless callback

Client callback state preserved through stateless callback
----------------------------------------------------------

                 Key: TUSCANY-2306
                 URL: https://issues.apache.org/jira/browse/TUSCANY-2306
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Core Runtime
    Affects Versions: Java-SCA-Next
            Reporter: Kevin Williams


Lines 650-654 of the Java CAA specification state:
     
"The difference for stateless services is that the callback field would not be available if the component is servicing a request for anything other than the original client. So, the technique used in the previous section, where there was a response from the backend Service which was forwarded as a callback from MyService would not work because the *callback field would be null* when the message from the backend system was received."

The test case org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback3 demosntrates that the callback field is not null when the message is received from the "back end service"

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

[jira] Assigned: (TUSCANY-2306) Client callback state preserved through stateless callback

Posted by "Simon Nash (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Nash reassigned TUSCANY-2306:
-----------------------------------

    Assignee: Simon Nash

> Client callback state preserved through stateless callback
> ----------------------------------------------------------
>
>                 Key: TUSCANY-2306
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2306
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>            Reporter: Kevin Williams
>            Assignee: Simon Nash
>             Fix For: Java-SCA-Next
>
>
> Lines 650-654 of the Java CAA specification state:
>      
> "The difference for stateless services is that the callback field would not be available if the component is servicing a request for anything other than the original client. So, the technique used in the previous section, where there was a response from the backend Service which was forwarded as a callback from MyService would not work because the *callback field would be null* when the message from the backend system was received."
> The test case org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback3 demosntrates that the callback field is not null when the message is received from the "back end service"

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

[jira] Resolved: (TUSCANY-2306) Client callback state preserved through stateless callback

Posted by "Simon Nash (JIRA)" <tu...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Nash resolved TUSCANY-2306.
---------------------------------

    Resolution: Fixed

A callback proxy was always being injected, even when the invocation creating the instance did not include a callback endpoint.  Fixed in revision 654860.

> Client callback state preserved through stateless callback
> ----------------------------------------------------------
>
>                 Key: TUSCANY-2306
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2306
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>            Reporter: Kevin Williams
>            Assignee: Simon Nash
>             Fix For: Java-SCA-Next
>
>
> Lines 650-654 of the Java CAA specification state:
>      
> "The difference for stateless services is that the callback field would not be available if the component is servicing a request for anything other than the original client. So, the technique used in the previous section, where there was a response from the backend Service which was forwarded as a callback from MyService would not work because the *callback field would be null* when the message from the backend system was received."
> The test case org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback3 demosntrates that the callback field is not null when the message is received from the "back end service"

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

[jira] Commented: (TUSCANY-2306) Client callback state preserved through stateless callback

Posted by "Simon Nash (JIRA)" <tu...@ws.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595393#action_12595393 ] 

Simon Nash commented on TUSCANY-2306:
-------------------------------------

I don't see the statelessCallback3 test in CallbackTestCase.java.  What is the revision number for the checkin?

> Client callback state preserved through stateless callback
> ----------------------------------------------------------
>
>                 Key: TUSCANY-2306
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2306
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Core Runtime
>    Affects Versions: Java-SCA-Next
>            Reporter: Kevin Williams
>
> Lines 650-654 of the Java CAA specification state:
>      
> "The difference for stateless services is that the callback field would not be available if the component is servicing a request for anything other than the original client. So, the technique used in the previous section, where there was a response from the backend Service which was forwarded as a callback from MyService would not work because the *callback field would be null* when the message from the backend system was received."
> The test case org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statelessCallback3 demosntrates that the callback field is not null when the message is received from the "back end service"

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