You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2010/06/15 14:57:23 UTC

[jira] Created: (TUSCANY-3594) SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI

SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI
------------------------------------------------------------------------------

                 Key: TUSCANY-3594
                 URL: https://issues.apache.org/jira/browse/TUSCANY-3594
             Project: Tuscany
          Issue Type: Sub-task
          Components: Java SCA Axis Binding Extension
    Affects Versions: Java-SCA-2.0-M5
         Environment: All
            Reporter: Simon Laws
             Fix For: Java-SCA-2.0


Currently the code flows an endpoint URI that the target end the uses to consult the registry, This won't work in and external web service wants to use the callback address so we need to flow the actual URL of the callback endpoint .

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


[jira] Resolved: (TUSCANY-3594) SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI

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

Simon Laws resolved TUSCANY-3594.
---------------------------------

    Resolution: Fixed

Fix applied

> SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI
> ------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3594
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3594
>             Project: Tuscany
>          Issue Type: Sub-task
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-2.0-M5
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> Currently the code flows an endpoint URI that the target end the uses to consult the registry, This won't work in and external web service wants to use the callback address so we need to flow the actual URL of the callback endpoint .

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


[jira] Assigned: (TUSCANY-3594) SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI

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

Simon Laws reassigned TUSCANY-3594:
-----------------------------------

    Assignee: Simon Laws

> SOAP header should flow a callback protocol URI rather than a SCA Endpoint URI
> ------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3594
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3594
>             Project: Tuscany
>          Issue Type: Sub-task
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-2.0-M5
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> Currently the code flows an endpoint URI that the target end the uses to consult the registry, This won't work in and external web service wants to use the callback address so we need to flow the actual URL of the callback endpoint .

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