Re: [xml-dev] From Pox to Pojo

["Pete Cordell" <petexmldev@tech-know-ware.com>]

Well, we do an XML to C++ databinding tool (as you might have gathered from 
the sig!), so I'll give my views...

I would say whether databinding is the right thing for a particular 
application depends very much on what the requirements are.

I think databinding works best for the more data oriented applications.  In 
particular, mixed content is not very well supported.  If your data is 
generally data oriented, but has, say, a blob of XHTML in it via an xs:any 
specification, then I'd still say databinding is still appropriate.  You'd 
use databinding to access the XTHML blob, and then process that using some 
other technique (possibly some kind of third-party browser module).

Also the more your XML data is a means to an end rather than an end in 
itself, then the more likely databinding is going to be a good fit.  By that 
I mean the more you can treat the XML side of things as a black box for your 
application, the more databinding will be good for you.  That doesn't mean 
that unmarshalling an XML instance into objects, twiddling them and then 
marshalling them out again isn't appropriate.  It's just that if that is 
your entire reason for existence, then it might be considered a bit lazy and 
you could probably do a more efficient job using something like XSLT or SAX. 
(Although - I would do the lazy route just because I am more familiar with 
it and already have all the tools!)

If your XML data is very large (where 'very large' depends on your system) 
then databinding might not be appropriate.  This is because databinding 
results in the entire XML instance being represented in memory.  I've never 
done any tests to get an idea of how the size of the XML instance compares 
with the amount of system memory consumed, but I would expect the consumed 
system memory to be less.

Databinding is also very handy if your data persists in the application for 
some time, and a number of different code modules dip in and out of it (such 
as configuration data).

HTH,

Pete.
--
=============================================
Pete Cordell
Codalogic
for XML Schema to C++ data binding visit
 http://www.codalogic.com/lmx/
=============================================

----- Original Message ----- 
From: "Andrew Welch" <andrew.j.welch@gmail.com>
To: <xml-dev@lists.xml.org>
Sent: Wednesday, October 10, 2007 10:08 AM
Subject: [xml-dev] From Pox to Pojo


> Given the baisc requirement of parsing some plain well-formed XML in
> Java and performing some operations on it, what's everyone using at
> the moment?
>
> After writing the XML Schema, I would normally have coded my own sax
> parser and pojos, but have been using XMLBeans instead (which could
> well have issues mentioned in the the other post) in attempt to move
> away from the long winded approach...
>
> So where's the technology at at the moment?  If the general feeling is
> that XML binding tools are ultimately an extra layer of hassle when it
> comes to the finer details then do people still code their own layers
> for reading/writing XML ?
>
>
>
> thanks
> -- 
> Andrew Welch
> http://andrewjwelch.com
> Kernow: http://kernowforsaxon.sf.net/
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>