cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: http: URLs and setepURL
Date Tue, 13 Mar 2007 02:00:51 GMT
On 3/12/07, Polar Humenn <phumenn@iona.com> 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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message