I don't know that there is a formal requirement that a Conduit be attached to a single host or attached to a host+path.
I also think you're exaggerating the problem of overriding the endpoint address. Typically people will want to use a different address for a development server instead of production. So their configuration is likely to apply to both. I don't really see any users just sticking in a random address there and having an issue with trusting a rogue server. If you have suggestions about how this should work, would love to hear them. On 3/13/07, Polar Humenn <[EMAIL PROTECTED]> wrote:
Aside from this being just plain wrong, there might be a requirement that the endpoint that the conduit is created with is just a URL with host information. Is it supposed to be the case that the EndpointInfo.getAddress() or EndpointReferenceType.getAddress() is only a URL of the form "http://host.com:1234"; or is there an associated path? In what situations is the PATH_INFO used? Is it part of the JAX-WS? Cheers, -Polar Dan Diephouse wrote: > On 3/12/07, Polar Humenn <[EMAIL PROTECTED]> wrote: > >> Shouldn't this conduit ONLY be sending messages to the endpoint >> designated (configured) for it? >> >> Furthermore, the code fragment in setupURL >> >> String result = value != null ? value : url.toString(); >> if (null != pathInfo && !result.endWith(pathInfo)) { >> result = result + pathInfo; >> } >> >> has a bit of a caveat in that you'd never be able to send a request to a >> location >> of "http://somewhere.com/xx/xx";, specified by a URL of >> "http://somwhere.com/xx"; a Message.PATH_INFO property of "/xx". >> >> Now some might say "why would you want to do that?" I know "xx" doesn't >> make sense to most, but what about, >> >> "http://somewhere.com/path/to/parent/.."; >> >> as a URL location built up from other things you might have dealt with, >> and you want to set a path from there to be "/.." Then you are in a >> completely different location than you want to be. >> >> Is there a specific "contract" are placed on Message.ENDPOINT_ADDRESS, >> Message.PATH_INFO for this situation, or its it a bug? > > > -1 to changing this. PATH_INFO is supposed to be all the stuff after the > host. Just like URI.getPath(). - > http://java.sun.com/j2se/1.5.0/docs/api/index.html?java/net/URI.html > > - Dan > >
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
