RE: LocationTemplate-2G

My intention was to use the raw template in a way that would create a
useable URI but not mess with the paths since that causes mapping problems
in Axis2.  I agree the uncited parameters get in the way.

More in line with this intention, we could simply set ignoreUncited, and the
expected result would be http://www.example.org/RawParameter#id.  I was
trying to get a raw template example without breaking the paths (I left that
to LocationTemplate-3G.)

That's what I've check in now.

Also, I note that my "data" test element is losing it's form a bit - some of
the "encoded" characters like * aren't supposed to be, while some that are
"unencoded" like & need to be.  Oh well...

Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
 

> -----Original Message-----
> From: Youenn Fablet [mailto:[email protected]]
> Sent: Thursday, February 22, 2007 12:14 AM
> To: Jonathan Marsh
> Cc: www-ws-desc
> Subject: LocationTemplate-2G
> 
> Working on LocationTemplate-2G, I have the following comments:
> 1) the schema does not define the 'fragment' parameter though it is used
> in the wsdl. I suggest adding it in the schema
> 2) the wsdl file is defining a location="RawParameter{!fragment}", the
> fragment value being "#id".
> In theory, we should build a URL like:
>     http://www.example.org/RawParameter#id?full-uri=...&path=...&data=...
> IIRC, a typical url is something like base_uri/path?query#fragment.
> The current location will then produce the following url:
>     http://www.example.org/RawParameter#id
>
> Since I do not think this is the intention, we may want to have a new
> location, like:
> 
> "RawParameter?full-uri={full-
> uri}&path={path}&data={data}&fragment={!fragment}"
> The corresponding url will then be something like:
>
> http://www.example.org/RawParameter?full-
> uri=...&path=...&data=...&fragment=#id
> Does this make sense?
>     Youenn