Andrea Aime ha scritto: > Martin Desruisseaux ha scritto: > ... >> * Why enabling JAXB and not Hibernate? Because JAXB is bundled >> in Java 6 and used by other Sun technologies around Glassfish, >> while Hibernate annotations would introduce a new dependency. > > See, that's a critical point, we have total different opinion > on what's a standard. > Glassfish is not the standard, Tomcat is. > EJB3 is not the standard, Spring and Hibernate are.
Ah, to provide some more backing, here are the Google trends statistics about what people are searching the net for, it gives a rough, but not totally misguided, view of the importance of each technology: http://www.google.com/trends?q=tomcat%2C+glassfish%2C+jboss%2C+jetty%2C+weblogic%2C+websphere+ http://www.google.com/trends?q=ejb3%2C+hibernate%2C+spring%2C+ejb2 I tried to make one up with jaxb as well, thought I'm not an expert of xml technologies, and it's true jaxb is well positioned: http://www.google.com/trends?q=jaxb%2C+xmlbeans%2C+jibx%2C+jaxme%2C+stax&ctab=0&geo=all&date=all&sort=1 If only it was able to parse multiple schemas into a single object model and the gml dynamic ones as well I would have no troubles with it. The key is to have a technology flexible enough to handle real world use cases without an explosion of model classes imho (or doing it at all, in the case of the WFS runtime generated GML schemas). Cheers Andrea ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
