> > Friday, almost evening... my head is spinning :) Right, you are thinking way to hard for a Friday :).
> > Anyways, looks like a good idea, but the Request objects should become > public. If we do that, the same object could also hold the Operation, > that is, accumulate information as it goes, and leave the exception > handlers figure out what they prefer to use. +1 > > Yet, is the parsed kvp set if an exception occurs > right during kvp parsing? Even in that case there is no guarantee > I'd get the widht/height/format in parsed format, I'd have to resort > using the kvp parsers manually anyways.... so I would have no > much use Operation or the parsed kvp, thought the raw kvp can be handy. Nope, teh complete parsing of kvp will always happen. Any exceptions that occur are caught, and set on the request object. So you can be sure the kvp's were parsed... but the one you are interested in could have been in err. So I guess some checks will need to be done. But in the normal case things like width and height and format will be fine. > >> So i guess the exception handler could get at the request if the >> service has not read it already... > > Yeah, this one too seems useful. So ok, exposing Request seems like > a good path. So, we move it to its own class? And then add getters and > setters for all the fields it has? Sounds good to me. > > Cheers > Andrea > > !DSPAM:4007,48370762304278362916074! > -- Justin Deoliveira The Open Planning Project [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
