Jody Garnett wrote: > johann sorel wrote: > >> We are using a JaxB solution. >> > That better be in your own code base then; you can make use of the > plug-in system to use your own implementation of the style objects. > StyleFactory at least is ready for you to swap implementations in and out. > Quick question; so I can understand ... how did you plan to use JaxB? Near as I can tell you would need jaxb binding for Filter, Expression and GML3? Will you be using the GeoAPI Geometry classes for the GML3 binding; or morphing down to JTS Geometry objects.
I am just trying to figure out (if JaxB is a technical direction your company is going in) what steps need to be taken. The plug-in system does offer you enough isolation that you can have a set of style objects with jaxb annotations; my recommendation would be to just use them as data transfer objects; and then use a style visitor to on the result to produce geotools style objects. I think Martin performed similar tricks to allow any metadata interface to be "copied" into the metadata implementation classes for persistence? If you have any questions about the geotools approach the developers guide has a good tutorial; and the existing SLD 1.0 bindings can offer a working example. Cheers, 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
