On 20-05-15 12:22, Andrea Aime wrote: > Hum... it would be the fourth object <-> xml technology we have in the > code base (old xml parsers/encoders, xsd parsers encoders, xstream). > From what it looks this one is in the same basket as xstream. > I don't want to sound against innovation, but we cannot either allow > everybody to go their merry > way and keep on piling up dependencies and programming styles that in > the end just make > it harder to undestand, maintain and evolve the code. > So, for these cases, I'd like to hear a solid agreement from the > community if its usage > goes beyond a isolated case in a unsupported module. >
OXM is actually not an object<-->xml mapping technology, but an abstraction of this mapping that allows many implementations. This abstraction comes with using spring rest api, and is mainly there to support implicit conversion in your spring controllers. The mapping implementation I used in geofence-server is actually called Jaxb. (The used xml annotations, by the way, are part of the java standard library.) Alternative implementations that can be used are xmlbeans, jibx OR xstream. So, to summarize, in order to switch to spring rest there is no absolute necessity to add another technology like jaxb, but there is a need for OXM though which would function as the bridge between spring rest and xstream. I think spring rest by itself is definitely an improvement in terms of "understand, maintain and evolve the code", although of course I agree that people can't just pile up new ways of doing things and agreement is necessary. I just picked up from Jody he was interested in switching to spring rest which is the main reason I suggested it. Also, geoserver already relies on spring so much that (apart from oxm) there is very little need for additional dependencies. Either way, I was mainly trying to figure out what to do with my code. I guess if there is no agreement then by default the user/role api will remain part of the geofence-server community module as part of the geofence rest server and it will need to be implemented as a restful service to become part of geoserver. Regards Niels ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
