You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Paul Fremantle (JIRA)" <ji...@apache.org> on 2007/03/21 11:19:32 UTC
[jira] Created: (SANDESHA2-74) "Replay" synchronous model not
working properly
"Replay" synchronous model not working properly
------------------------------------------------
Key: SANDESHA2-74
URL: https://issues.apache.org/jira/browse/SANDESHA2-74
Project: Sandesha2
Issue Type: Bug
Environment: Axis2 talking to .NET
Reporter: Paul Fremantle
This is fairly complex :-)
I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID.
In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out).
Therefore the hack is causing an exception.
--
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] Resolved: (SANDESHA2-74) "Replay" synchronous model not
working properly
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chamikara Jayalath resolved SANDESHA2-74.
-----------------------------------------
Resolution: Fixed
Assignee: Chamikara Jayalath
TerminateSequence actionMapping was moved to the InOnlyOperation.
> "Replay" synchronous model not working properly
> ------------------------------------------------
>
> Key: SANDESHA2-74
> URL: https://issues.apache.org/jira/browse/SANDESHA2-74
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 talking to .NET
> Reporter: Paul Fremantle
> Assigned To: Chamikara Jayalath
>
> This is fairly complex :-)
> I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
> After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID.
> In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out).
> Therefore the hack is causing an exception.
--
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] Resolved: (SANDESHA2-74) "Replay" synchronous model not
working properly
Posted by "Chamikara Jayalath (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chamikara Jayalath resolved SANDESHA2-74.
-----------------------------------------
Resolution: Fixed
Assignee: Chamikara Jayalath
TerminateSequence actionMapping was moved to the InOnlyOperation.
> "Replay" synchronous model not working properly
> ------------------------------------------------
>
> Key: SANDESHA2-74
> URL: https://issues.apache.org/jira/browse/SANDESHA2-74
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 talking to .NET
> Reporter: Paul Fremantle
> Assigned To: Chamikara Jayalath
>
> This is fairly complex :-)
> I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
> After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID.
> In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out).
> Therefore the hack is causing an exception.
--
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-74) "Replay" synchronous model not
working properly
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482704 ]
Matt Lovett commented on SANDESHA2-74:
--------------------------------------
Sounds like we need to update the module.xml (plus the operation code in SpecSpecificConstants) to make the operations used for RM match the defintinons in the 1.0 and 1.1 specs. We have discussed this on-list in the past.... the 'wrong' operations were used to fool the transport into doing the right thing, but I think we need to use the right operations, and fix the transport to handle the wire flows that arrive. With a bit of luck the old issues will already have been resolved...
> "Replay" synchronous model not working properly
> ------------------------------------------------
>
> Key: SANDESHA2-74
> URL: https://issues.apache.org/jira/browse/SANDESHA2-74
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 talking to .NET
> Reporter: Paul Fremantle
>
> This is fairly complex :-)
> I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
> After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID.
> In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out).
> Therefore the hack is causing an exception.
--
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-74) "Replay" synchronous model not
working properly
Posted by "Matt Lovett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANDESHA2-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482704 ]
Matt Lovett commented on SANDESHA2-74:
--------------------------------------
Sounds like we need to update the module.xml (plus the operation code in SpecSpecificConstants) to make the operations used for RM match the defintinons in the 1.0 and 1.1 specs. We have discussed this on-list in the past.... the 'wrong' operations were used to fool the transport into doing the right thing, but I think we need to use the right operations, and fix the transport to handle the wire flows that arrive. With a bit of luck the old issues will already have been resolved...
> "Replay" synchronous model not working properly
> ------------------------------------------------
>
> Key: SANDESHA2-74
> URL: https://issues.apache.org/jira/browse/SANDESHA2-74
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2 talking to .NET
> Reporter: Paul Fremantle
>
> This is fairly complex :-)
> I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
> After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID.
> In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out).
> Therefore the hack is causing an exception.
--
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