axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eran Chinthaka (JIRA)" <>
Subject [jira] Commented: (AXIS2-885) Enhance support for the WS-Addressing anonymous and none URIs
Date Thu, 13 Jul 2006 08:05:31 GMT
    [ ] 

Eran Chinthaka commented on AXIS2-885:

Hi Brian,

I really appreciate this patch. But let me raise a small quesion about defaulting the To value
to anonymous URI.

You might already know that the reason for having To EPR inside message context has nothing
to do with the presense of a To header in a SOAP message. Basically message context has some
"Addressing like" properties to capture those parameters which can be filled by anyone, including
Addressing Handlers and transport handlers. 
So with that logic, I don't think its correct to call messageContext.setTo(new EndpointReference(Final.WSA_ANONYMOUS_URL))
when there isn't a To header in the message. The msgCtxt's To value is may be already been
set by transport, in which case we don't wanna override.
I hope you can remember that the intention of our AddressingHandlers is to extract addressing
information from the information available in the SOAP message and set them to the message
I know its bit of difficult to understand and Addressing spec wanted to default To and ReplyTo
to anon uris, but it was by design that we did it. 


> Enhance support for the WS-Addressing anonymous and none URIs
> -------------------------------------------------------------
>          Key: AXIS2-885
>          URL:
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement

>   Components: core
>     Reporter: Brian DePradine
>  Attachments: patch.txt
> Ensure that the semantics associated with the anonymous and none URIs are fully supported.
In particular the anonymous URI indicates that any response should be synchronous, possibly
using the outbound stream of the inbound connection. The none URI indicates that no response
should be sent. Patch to follow.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message