Call physical targetAddress and wsa:To

[thomas.diesler]

/wsa:To

This OPTIONAL element (whose content is of type xs:anyURI) provides the value for the [destination] property. If this element is NOT present then the value of the [destination] property is "http://www.w3.org/2005/08/addressing/anonymous".

Currently CallImpl uses this logic to derrive the physical target address. Is this right?

 // Use Stub.ENDPOINT_ADDRESS_PROPERTY
 String targetAddress = getTargetEndpointAddress();

 // Fall back to wsa:To
 AddressingConstantsImpl ADDR = new AddressingConstantsImpl();
 AddressingProperties addrProps = (AddressingProperties)msgContext.getProperty(JAXWSAConstants.CLIENT_ADDRESSING_PROPERTIES_OUTBOUND);
 if (targetAddress == null && addrProps != null && addrProps.getTo() != null)
 {
 String wsaTo = addrProps.getTo().getURI().toString();
 if (wsaTo.equals(ADDR.getAnonymousURI()) == false)
 {
 try
 {
 URL wsaToURL = new URL(wsaTo);
 log.debug("Sending request to addressing destination: " + wsaToURL);
 targetAddress = wsaToURL.toExternalForm();
 }
 catch (MalformedURLException ex)
 {
 log.debug("Not a valid URL: " + wsaTo);
 }
 }
 }

 // The endpoint address must be known beyond this point
 if (targetAddress == null)
 throw new WSException("Target endpoint address not set");

[thomas.diesler]

The questions I have are:

1. Is it correct to prefer the soap:address from the wsdl?
2. Should wsa:To ever be used as physical address?

[jason.greene]

<wsa:To> is supposed to be used for routing, so since we aren't acting as a router I don't think we need to look at it. If we are acting as a router then the method for mapping the logical to physical locations is not part of WSA, and is implementation specific.

Although there is Microsoft a microsoft spec out there for mapping them (WS-Referral):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnglobspec/html/wsreferspecindex.asp


A good, yet old article that talks about wsa:to is here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/html/wsroutetowsadd.asp

-Jason

[hbraun]

I think Jason is right. It's solely used as routing information and therefore it must not be used as the physical address of the target endpoint. I.e. WS-Eventing makes use of this behaviour. We can ignore it, but the addressing handlers need to supply the wsa:To defaults if it's not set.

[hbraun]

There's actually one case i can think of, when we need to act upon wsa:To addresses, which is stateful messaging using SFSB as web service implementations.