axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-221) Axis2 Addressing does not handle the reference parameters correctly (Eg: Reply To EPR ref props)
Date Sun, 09 Oct 2005 14:29:48 GMT
    [ 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


Mime
View raw message