The ones that use configuration and bindings ( to map XML snippets to java
objects ).
I just mention this as GeoServer bounced an initial JAXB implementation of
SOS due to the duplication of parsers / schema.
http://docs.geotools.org/latest/userguide/library/xml/internal/tutorial.html
--
Jody Garnett
On 29/10/2012, at 6:50 PM, "Ákos Maróy" <[email protected]> wrote:
On 29/10/12 21:47, Jody Garnett wrote:
Sounds great - please consider using our GML parseres rather than JAXB
so we do not have to have all the schemas in memory twice.
which parsers would that be?
also, the GML-based data I'm using is stored in a considerably large set
of other XML data, which is also defined by XML Schemas. hence my usage
of JAXB, so that I have an API to manipulate the whole data set
generated automatically from the schema.
is it possbile to mix both of these worlds somehow?
------------------------------------------------------------------------------
The Windows 8 Center - In partnership with Sourceforge
Your idea - your app - 30 days.
Get started!
http://windows8center.sourceforge.net/
what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
