Adrian Custer wrote: > Hey Jody, > > This is a surprising email from you, unusually full of stop energy. > Oh? I have talked about JaxB and its limitations before; this is why we don't use it very much ... > Could you explain why JAXB annotations are not a solution that fits in > with what GeoTools is for? Sure; we like to support multiple different XML file formats; for the same content. Ie our Filter classes can be made from CQL, Filter 1.0 and Filter 1.1 ... JaxB annotations would limit us to one flavour of XML. That is the top problem.
The other one comes down to the ability to handle schema extensions "extended". GML3 may define Geometry; but ISO makes it pretty clear that you can extend the Geometry primitives into your own domain ... a trick JaxB could never follow. If that is too crazy a consider just a normal Feature; every single Feature in the real world has to extend AbstractFeature; does JaxB go up the superclass chain in order to sort this out? > I know you have hesitations that perhaps that family of annotations is not > mature enough for all future needs but that seems very vague a notion to stop > people from writing the code they wishto write. So no, we can't merely say no > because it's an easy word to use. Well this is an open source project; and by definition a constant negotiation. JaxB does not fit in with my assumptions; and based on the two items above I hard pressed to see how it fits in with anyones assumptions. That is why I did not take part in a JaxB brindings for OGC models project; and why I don't want GeoTools to become the same thing ... That project (I think) made different beans for Filter 1.0 and Filter 1.1; you could pull off something like that - with each set of beans implementing the same GeoAPI Filter interfaces. But then you are into a mess of copying visitors in order to treat the beans as DTO objects... > What we could do would be to construct a series of serious technical > arguments or worries which could each be assessed on their merit. Sounds perfect. > So what are your concerns? Does JAXB prevent you from working in some way? > Does it stop your parser from working? I know nothing about this one way > or the other so can't help you construct such a list. We cannot however > resolve anything if we can't define it. > > You are busy this week so perhaps you cannot do this now but 'just say > no' has not been part of this project for the past decade so there is no > reason to start now. > Understood; and thanks for being the voice of reason. I thought I had calmly said no to JaxB several times over the last year; but perhaps it was overlooked (I write too much email and sometimes I am not blunt enough to be clear). Thanks muchly; and for understanding about my busy week. Jody ------------------------------------------------------------------------- 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
