As I have already said, I am not against JAXB at all, I am just asking if you could avoid annotating core modules because these of these objections:
- we are making tech choice and forcing or at least strongly suggesting (a user who wants to choose another technology will feel like taking the wrong path) users to adhere to this technology - I would prefer not to annotate core classes for two reasons: 1> it increases code size (we can play with that though) 2> things get messy if then we, or a user decde to use different annotations for another tool (I am sorry if someone is not happy, but this is a strong argument to me) - I do not care much about SUN vs non-SUN, unless the fact that using something because it is in the JDK or because sun wrote it, does not represent a strong argument to me. Summarising, I would rather prefer some sort of factory mechanism that would hide the annotations from the core modules (or whatever solution you may come up with). Simone. On Thu, Jun 26, 2008 at 12:25 PM, Martin Desruisseaux <[EMAIL PROTECTED]> wrote: > 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 > -- ------------------------------------------------------- Eng. Simone Giannecchini President /CEO GeoSolutions S.A.S. Via Carignoni 51 55041 Camaiore (LU) Italy phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it ------------------------------------------------------- ------------------------------------------------------------------------- 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
