From: Justin D. <jde...@op...> - 2010-11-30 15:19:45
|
On Tue, Nov 30, 2010 at 8:06 AM, Andrea Aime <and...@ge...>wrote: > On Tue, Nov 30, 2010 at 3:47 PM, Justin Deoliveira <jde...@op...> > wrote: > > I like the idea, but i agree I don't think it is something we can turn on > by > > default for reasons you stated. I think the code mappings make sense as > > well. > > Roger for the OWS 1.0 based protocols. > Wondering, what shall we do for WCS 1.1 and WPS 1.0 though? > For those the OWS 1.1 spec says to return status proper status codes. > I guess the DefaultServiceExceptionHandler can use some flag to decide > whether to use the http error codes or not, whilst the > OWS11ServiceExceptionHandler > should just set the status codes? > Opinions? > Yeah I think that approach makes sense since the spec supports it and I don't know of many clients built from those specific services so any change will probably have minimal impact. A couple of questions: 1. How are we going to go about registing the code to http code mappings? Will they be fixed? or will a particular service be able to add its own mappings? 2. Will we ever want to return specific codes other than 400 and 500. For example consider the case of a client requesting a layer that does not exist. A 404 would also make sense in this case. > Cheers > Andrea > > ----------------------------------------------------- > Ing. Andrea Aime > Senior Software Engineer > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584962313 > fax: +39 0584962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ----------------------------------------------------- > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. |