You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/03/21 12:49:32 UTC
[jira] Created: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
ws-makeconnection being used with WSRM1.0
-----------------------------------------
Key: SANDESHA2-76
URL: https://issues.apache.org/jira/browse/SANDESHA2-76
Project: Sandesha2
Issue Type: Bug
Environment: Axis2 and Sandesha2 latest builds
Reporter: Paul Fremantle
Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header>
<wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
<wsa:ReplyTo>
<wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
</wsa:ReplyTo>
<wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
<wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
</soapenv:Header>
<soapenv:Body>
<wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
<wsrm:AcksTo>
<wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
</wsrm:AcksTo>
<wsrm:Offer>
<wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
</wsrm:Offer>
</wsrm:CreateSequence>
</soapenv:Body>
</soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Commented: (SANDESHA2-76) ws-makeconnection being used with WSRM1.0
Posted by Paul Fremantle <pz...@gmail.com>.
Ok. Personally I think that mixing MakeConnection with RM1.0 is a bit
of a mess, and I can't see anyone else doing it. So here is my
proposal - we make it off by default and we add an explicit option to
allow it to be enabled. At the moment the default if you try and use
sync two-way RM with .NET is that we use MC headers. From an interop
perspective that is a nightmare, and the fact is that our main aim
with RM 1.0 should be interop with .NET and JAXWS RI.
Paul
On 3/21/07, Matt Lovett (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482742 ]
>
> Matt Lovett commented on SANDESHA2-76:
> --------------------------------------
>
> You can turn off the use of the RM-anon URI in the sandesha module.xml, there is a section that looks like this:
>
> <sandesha2:MakeConnection>
> <sandesha2:Enabled>true</sandesha2:Enabled>
> <sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
> </sandesha2:MakeConnection>
>
>
> I guess you may be arguing that we should automatically turn it off for RM 1.0 apps, but I'm not sure I agree. I still don't believe that the replay-requests approach works (it implies that the sequences are linked, and as you have noted, it forces a terminate to 'piggyback' where you would not expect it) - and I think using MakeConnection with WSRM 1.0 provides an interesting alternative. I'm happy to support both approaches.
>
> > ws-makeconnection being used with WSRM1.0
> > -----------------------------------------
> >
> > Key: SANDESHA2-76
> > URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> > Project: Sandesha2
> > Issue Type: Bug
> > Environment: Axis2 and Sandesha2 latest builds
> > Reporter: Paul Fremantle
> >
> > Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> > <?xml version='1.0' encoding='UTF-8'?>
> > <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> > <soapenv:Header>
> > <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> > <wsa:ReplyTo>
> > <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> > </wsa:ReplyTo>
> > <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> > <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> > </soapenv:Header>
> > <soapenv:Body>
> > <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> > <wsrm:AcksTo>
> > <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> > </wsrm:AcksTo>
> > <wsrm:Offer>
> > <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> > </wsrm:Offer>
> > </wsrm:CreateSequence>
> > </soapenv:Body>
> > </soapenv:Envelope>0
>
> --
> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Commented: (SANDESHA2-76) ws-makeconnection being used with WSRM1.0
Posted by Paul Fremantle <pz...@gmail.com>.
Ok. Personally I think that mixing MakeConnection with RM1.0 is a bit
of a mess, and I can't see anyone else doing it. So here is my
proposal - we make it off by default and we add an explicit option to
allow it to be enabled. At the moment the default if you try and use
sync two-way RM with .NET is that we use MC headers. From an interop
perspective that is a nightmare, and the fact is that our main aim
with RM 1.0 should be interop with .NET and JAXWS RI.
Paul
On 3/21/07, Matt Lovett (JIRA) <ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482742 ]
>
> Matt Lovett commented on SANDESHA2-76:
> --------------------------------------
>
> You can turn off the use of the RM-anon URI in the sandesha module.xml, there is a section that looks like this:
>
> <sandesha2:MakeConnection>
> <sandesha2:Enabled>true</sandesha2:Enabled>
> <sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
> </sandesha2:MakeConnection>
>
>
> I guess you may be arguing that we should automatically turn it off for RM 1.0 apps, but I'm not sure I agree. I still don't believe that the replay-requests approach works (it implies that the sequences are linked, and as you have noted, it forces a terminate to 'piggyback' where you would not expect it) - and I think using MakeConnection with WSRM 1.0 provides an interesting alternative. I'm happy to support both approaches.
>
> > ws-makeconnection being used with WSRM1.0
> > -----------------------------------------
> >
> > Key: SANDESHA2-76
> > URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> > Project: Sandesha2
> > Issue Type: Bug
> > Environment: Axis2 and Sandesha2 latest builds
> > Reporter: Paul Fremantle
> >
> > Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> > <?xml version='1.0' encoding='UTF-8'?>
> > <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> > <soapenv:Header>
> > <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> > <wsa:ReplyTo>
> > <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> > </wsa:ReplyTo>
> > <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> > <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> > </soapenv:Header>
> > <soapenv:Body>
> > <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> > <wsrm:AcksTo>
> > <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> > </wsrm:AcksTo>
> > <wsrm:Offer>
> > <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> > </wsrm:Offer>
> > </wsrm:CreateSequence>
> > </soapenv:Body>
> > </soapenv:Envelope>0
>
> --
> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482998 ]
Chamikara Jayalath commented on SANDESHA2-76:
---------------------------------------------
Matt, Paul,
I don't think we should be sending WSRM Anon URI for WSRM 1.0. This could easily cause interop issues. Is there any reason not to disable it ? (We can either make the UseRMAnonURI policy 'false' by default or we can stop the overriding addressing Anon URI for WSRM 1.0 ).
At the moment we are not sending any MC headers with WSRM 1.0 messages.
Chamikara
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Paul Fremantle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482761 ]
Paul Fremantle commented on SANDESHA2-76:
-----------------------------------------
Ok. Personally I think that mixing MakeConnection with RM1.0 is a bit
of a mess, and I can't see anyone else doing it. So here is my
proposal - we make it off by default and we add an explicit option to
allow it to be enabled. At the moment the default if you try and use
sync two-way RM with .NET is that we use MC headers. From an interop
perspective that is a nightmare, and the fact is that our main aim
with RM 1.0 should be interop with .NET and JAXWS RI.
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482998 ]
Chamikara Jayalath commented on SANDESHA2-76:
---------------------------------------------
Matt, Paul,
I don't think we should be sending WSRM Anon URI for WSRM 1.0. This could easily cause interop issues. Is there any reason not to disable it ? (We can either make the UseRMAnonURI policy 'false' by default or we can stop the overriding addressing Anon URI for WSRM 1.0 ).
At the moment we are not sending any MC headers with WSRM 1.0 messages.
Chamikara
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Paul Fremantle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482761 ]
Paul Fremantle commented on SANDESHA2-76:
-----------------------------------------
Ok. Personally I think that mixing MakeConnection with RM1.0 is a bit
of a mess, and I can't see anyone else doing it. So here is my
proposal - we make it off by default and we add an explicit option to
allow it to be enabled. At the moment the default if you try and use
sync two-way RM with .NET is that we use MC headers. From an interop
perspective that is a nightmare, and the fact is that our main aim
with RM 1.0 should be interop with .NET and JAXWS RI.
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482742 ]
Matt Lovett commented on SANDESHA2-76:
--------------------------------------
You can turn off the use of the RM-anon URI in the sandesha module.xml, there is a section that looks like this:
<sandesha2:MakeConnection>
<sandesha2:Enabled>true</sandesha2:Enabled>
<sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
</sandesha2:MakeConnection>
I guess you may be arguing that we should automatically turn it off for RM 1.0 apps, but I'm not sure I agree. I still don't believe that the replay-requests approach works (it implies that the sequences are linked, and as you have noted, it forces a terminate to 'piggyback' where you would not expect it) - and I think using MakeConnection with WSRM 1.0 provides an interesting alternative. I'm happy to support both approaches.
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
[jira] Commented: (SANDESHA2-76) ws-makeconnection being used with
WSRM1.0
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482742 ]
Matt Lovett commented on SANDESHA2-76:
--------------------------------------
You can turn off the use of the RM-anon URI in the sandesha module.xml, there is a section that looks like this:
<sandesha2:MakeConnection>
<sandesha2:Enabled>true</sandesha2:Enabled>
<sandesha2:UseRMAnonURI>true</sandesha2:UseRMAnonURI>
</sandesha2:MakeConnection>
I guess you may be arguing that we should automatically turn it off for RM 1.0 apps, but I'm not sure I agree. I still don't believe that the replay-requests approach works (it implies that the sequences are linked, and as you have noted, it forces a terminate to 'piggyback' where you would not expect it) - and I think using MakeConnection with WSRM 1.0 provides an interesting alternative. I'm happy to support both approaches.
> ws-makeconnection being used with WSRM1.0
> -----------------------------------------
>
> Key: SANDESHA2-76
> URL: https://issues.apache.org/jira/browse/SANDESHA2-76
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 and Sandesha2 latest builds
> Reporter: Paul Fremantle
>
> Just look at this message: It mixes a WSRM1.0 create sequence with a WSMakeConnection anon address! ARGG!
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header>
> <wsa:To>http://localhost:8080/PaulsService/mex</wsa:To>
> <wsa:ReplyTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:CEE46708042C2B84BF1174477542290</wsa:MessageID>
> <wsa:Action>http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence</wsa:Action>
> </soapenv:Header>
> <soapenv:Body>
> <wsrm:CreateSequence xmlns:wsrm="http://schemas.xmlsoap.org/ws/2005/02/rm">
> <wsrm:AcksTo>
> <wsa:Address>http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=urn:uuid:CEE46708042C2B84BF1174477542272</wsa:Address>
> </wsrm:AcksTo>
> <wsrm:Offer>
> <wsrm:Identifier>urn:uuid:CEE46708042C2B84BF1174477542070</wsrm:Identifier>
> </wsrm:Offer>
> </wsrm:CreateSequence>
> </soapenv:Body>
> </soapenv:Envelope>0
--
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org