On Wed, 2008-06-25 at 10:23 -0400, Chris Holmes wrote:
> if we're just talking about bringing in yet
> another XML then I think we need to seriously consider the downside of
> requiring our users to learn another technology.
As I understand Martin's vision, users are not forced to even think
about the annotations, which users can happily ignore. They are
annotations, not code, and invisible in the javadoc.
1) The modules which wish to add the annotations which they want but
commit to cover their whole module with those annotations targeting one
particular specification version.
This gives users who wish to use those annotations access to
them. For JAXB, annotated modules, this means those modules can
be serialized to one particular format. The rest of the world
can ignore them.
2) Those who wish to target or support multiple formats have more work
and will have to use either Justin's parser work or write code following
Jody's suggested DTO work. Both will work happily against the annotated
base class.
So the Java code works for everyone, there are two approaches for highly
complex parsing of different formats, and one default for the lazy
mortals that need one serializable format and are willing to settle for
"whatever SUN cooked up for us".
hope that helps explain things,
--adrian
-------------------------------------------------------------------------
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
