Quote away! And feel free to refactor/copy into a post on your blog. I'd keep a blog, but it's hard enough to remember to eat during the day...let alone get content up into a blog!
--saul On Tue, 2008-03-04 at 09:25 -0800, Jody Garnett wrote: > Thanks Saul; now if only you had a blog to post that on - it is > certainly the kind of background information a lot of us would find > useful. Can I quote some of this for the user guide? > > Jody > > Good morning Jody, > > > > It took me about 3 days to get up to speed on the xml-xsd parser, and to > > implement bindings that read an xml document and generated the > > appropriate domain objects. > > > > I'll share my EXTREMELY LIMITED AND DEFINITELY INCOMPLETE/POSSIBLY > > INACCURATE analysis of what I've figured out from using the various > > xmlschema binding frameworks I've used in my career. > > > > First, note that there are two parts to java-ifying an XML-schema based > > model: generating java domain objects--the actual objects that you're > > trying to parse the XML "into"--and generating some classes/code which > > does said parsing (often called "marshalling" or "unmarshalling"). > > The different technologies you list below do different parts of this, > > some making one or the other part optional. > > > > JAXB: generates domain objects from schema, and provides a "smart" > > parser/marshaller that reads XML documents and turns them into the > > generated domain objects. Often the domain objects "feel" like the XML > > they were generated from. As will all big technologies, you can get > > JAXB to do anything (*just* the marshalling, *just* the domain object > > generation, cut your hair, wash your car), so your mileage/abilities > > with JAXB will vary depending on the amount of time you put into it. > > > > XDO and XML-XSD: these are purely "marshalling" technologies. XML-XSD > > has some cool extensions allowing you to auto-marshall to a generated > > EMF model of domain objects. One criticism of the EMF domain objects is > > that they definitely "feel" very EMFy. > > > > XStream: I have zero hands-on experience with this one. I think Justin > > played extensively with this technology a while ago, so he might have > > more advice. > > > > There's also XMLBeans, which is fairly similar to JAXB, but might be so > > old that it's fallen out of favor with anyone sane. > > > > > > Good luck jody! > > --saul > > > > > > > > > > > > > > > > On Mon, 2008-03-03 at 17:19 -0800, Jody Garnett wrote: > > > >> Morning Saul; > >> > >> I am looking at the WPS specification (a lot to like actually) and > >> considering the various options for handling the XML side of things. A > >> lot of technologies are around these days: > >> - Martin is using JAXB for metadata > >> - We use the "XDO" parser for GML2 > >> - Gabriel is working on the binding side of things for WFS 1.1 / GML3 > >> - XStream gets a lot of good press > >> - and so on ... > >> > >> How long did it take you to do up bindings for WMS (and are we ever > >> going to ditch the "XDO" bindings?). > >> It feels like doing bindings for WPS is overkill; but their is GML in > >> the mix so ... > >> Jody > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Geotools-devel mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/geotools-devel > >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
