Okay, one last try to explain:
* You objected that putting JAXB annotations would
prevent usage of other annotations like Hibernete
WRONG: Each annotations live in their own packages.
* You objected that putting JAXB annotations would prevent
users to extend those classes with their own annotations.
As far as I known, users would need to modify the source
code for doing that (putting annotations right in the
appropriate classes). So nothing change for them. Quite
the opposite, it is easier for users to modify a set of
existing annotations than writting all of them.
* On "Why JAXB and not Hibernate", Andrea said that there
is standardized annotations that Hibernate recognizes.
If this is standard, then I'm all for declaring them.
Are they standard? I mean the annotations AND the
database schema. With JAXB annotations, the XML schema
is standard: ISO 19139.
* You objected about the multiplicity of XML parsing methods.
JAXB is *invisible* in the API. They *enable* usage of those
metadata classes in SUN technologies. If you don't like SUN
technologies, nothing force you to use them.
* I offered many time to setup an system of different GeoTools
flavors (this is needed anyway), given users the choice between
metadata with and without JAXB. Why this is not suffisient for
cooling down this issue?
Martin
-------------------------------------------------------------------------
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
