You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Thilina Gunarathne (JIRA)" <ji...@apache.org> on 2005/09/15 11:51:54 UTC
[jira] Created: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
------------------------------------------------------------------------------------------------
Key: AXIS2-221
URL: http://issues.apache.org/jira/browse/AXIS2-221
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Thilina Gunarathne
Assigned to: Eran Chinthaka
Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=all ]
Thilina Gunarathne updated AXIS2-221:
-------------------------------------
type: Improvement (was: Bug)
Priority: Minor (was: Critical)
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Minor
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-221) Axis2 Addressing does not handle the
reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=all ]
Eran Chinthaka resolved AXIS2-221:
----------------------------------
Resolution: Fixed
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Minor
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=all ]
Thilina Gunarathne updated AXIS2-221:
-------------------------------------
Priority: Critical (was: Major)
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Critical
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=comments#action_12331667 ]
Eran Chinthaka commented on AXIS2-221:
--------------------------------------
Thilina,
When you send some reference parameters to the server, as reference parameters in the replyTo epr, they will send back to the as top level headers in the response message.
For example consider you are sending a message with following ReplyTo EPR.;
<wsa:ReplyTo>
.................................
. ............................
<wsa:ReferenceParameters>
<fabrikam:CustomerKey>123456789</fabrikam:CustomerKey>
<fabrikam:ShoppingCart>ABCDEFG</fabrikam:ShoppingCart>
</wsa:ReferenceParameters>
</wsa:ReplyTo>
When we formulate the response message, yes we do send them back. BUT, there is a difficulty in identifying them depending on the WS-A version that is being used.
If its Submission version there is no way to identify whether a given SOAP Header is a reference parameter or not. But if it is the WS-A Final version that you use, then all reference parameters which are appearing in the SOAP header will contain an attribute to identify them as a reference parameter.
For example, the reponse message will contain something like this;
<env:Header>
............................
<fabrikam:CustomerKey wsa:IsReferenceParameter='true'>123456789</fabrikam:CustomerKey>
<fabrikam:ShoppingCart wsa:IsReferenceParameter='true'>ABCDEFG</fabrikam:ShoppingCart>
.......................
</env:Header>
In this case Addressing handler should identify them and populate the To epr. So this is a problem with WS-A submission spec and not with our implementation. (If you are still not clear, please go and read WS-A Submission and Final specifications.)
So to overcome this, I think we need to do something like what Sanjiva has suggested. But that is yet to be done. So do not consider this as a bug in Axis2.
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Critical
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Sanjiva Weerawarana (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=comments#action_12331666 ]
Sanjiva Weerawarana commented on AXIS2-221:
-------------------------------------------
To fix this we need to introduce a parameter to the WS-Addr module to config that on a per-service basis with the QNames of the headers which are to be treated as reference parameters. In order to support this it'll be necessary for the addr module to insert a post-dispatch handler which will look at the service specific property and do the extra work of identifying and extracting the WS-A submission ref params (which are not tagged unlike WS-A final ones).
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Critical
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=comments#action_12331710 ]
Thilina Gunarathne commented on AXIS2-221:
------------------------------------------
Yes.. Agreed.. I'm not saying it's a bug.
Sorry for the misunderstanding caused by my comment . Pls notice the comment I've mentioned. It says that the original bug is fixed.
>>Axis2 now extracts the Reference parameters... (I checked reference parameters only.)
Currently in Kandula what we are doing is accessing the Envelope through the message context and looks for the Qname of the reference property.
IMHO accessing the envelope inside the business logic method impl is not a good practice to suggest to the users. That's why we need something like what Dr.Sanjiva is suggesting.
It seems I have mistakenly prioratise the issue. Priority should be an *improvement*.
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
> Priority: Critical
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Posted by "Thilina Gunarathne (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-221?page=comments#action_12331664 ]
Thilina Gunarathne commented on AXIS2-221:
------------------------------------------
Axis2 now extracts the Reference parameters... (I checked reference parameters only.)
When using WSA-Submission Axis2 still does not recognise or extracts the reference properties in the header. Axis2 cannot handle the following.....
<soap:Header>
....................
<wsa:To soap:mustUnderstand="1"> .................................. </wsa:To>
<footx:TransactionID>
uuid:ac4c2599-0ad9-4b88-ac33-12b765390929
</footx:TransactionID>
<footx:EnlistmentID>
12cab914-ec4d-400c-ac2f-47a9b9228b5b
</footx:EnlistmentID>
</soap:Header>
> Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-221
> URL: http://issues.apache.org/jira/browse/AXIS2-221
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Thilina Gunarathne
> Assignee: Eran Chinthaka
>
> Current AddressingInHandler does not extract and set the reference properties in Reply TO EPR.
> I have a client which sets a reference parameter to the Reply To EPR of the outgoing message. It expects the property to be returned in the response message as a reference parameter.. This does not happen in current Axis2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira