From: Jody G. <jod...@gm...> - 2012-10-29 21:16:02
|
The parser is open ended, you can register more bindings for your domain objects. So if you wanted you could try and pass over control to JAXB be on the trailing edge of one of your tags ( like a pull parser ). Or just write bindings. Finally on the off chance you are using an EMF model it can short cut the need to generate bindings. Note this also does encoding. I usually call it "Schema assisted". Well feature collection is the main thing. Please have a look at the app-Schema work for a working design. -- Jody Garnett On 29/10/2012, at 7:09 PM, "Ákos Maróy" <ak...@ma...> wrote: On 29/10/12 22:04, Jody Garnett wrote: 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 I see your point my concern is of having to manually convert / map the GML constructs into 'features' as required by a GeoTools data store. is there anything already existing that would simplify this task? |