This was something we (saul) added after the fact, and you are correct
it has no mention in the xsd. The reason we added it is because we
needed to associate the request url being made by the client with the
request object. The reason being that the request object is the only
object that makes its way through the entire dispatch chain. This is how
the old dispatch system did it as well.
Gabriel Roldán wrote:
Hey, a quick one:
what the baseUrl property of BaseRequestType is and where does it come from?
As its not part of the request's xsd model, I guess its a legacy property we
might use as metadata for the responses that require referencing a resource
(like to direct schema locations to geosrever DescribeFeatureType requests
and stuff?)
cheers,
Gabriel
!DSPAM:4007,472ef1be15362458217002!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
yeah, it makes sense. Thanks for confirming that.
So its something geoserver sets programatically, not something that needs to
be parsed. Gotcha.
Gabriel
On Monday 05 November 2007 04:39:22 pm Justin Deoliveira wrote:
This was something we (saul) added after the fact, and you are correct
it has no mention in the xsd. The reason we added it is because we
needed to associate the request url being made by the client with the
request object. The reason being that the request object is the only
object that makes its way through the entire dispatch chain. This is how
the old dispatch system did it as well.
Gabriel Roldán wrote:
> Hey, a quick one:
> what the baseUrl property of BaseRequestType is and where does it come
> from?
>
> As its not part of the request's xsd model, I guess its a legacy property
> we might use as metadata for the responses that require referencing a
> resource (like to direct schema locations to geosrever
> DescribeFeatureType requests and stuff?)
>
> cheers,
>
> Gabriel
>
> !DSPAM:4007,472ef1be15362458217002!