Meaningless Drivel is fun!
The moose likes XML and Related Technologies and the fly likes Serious JAXB Limitation? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » XML and Related Technologies
Bookmark "Serious JAXB Limitation?" Watch "Serious JAXB Limitation?" New topic

Serious JAXB Limitation?

James Montgomery

Joined: Jan 29, 2003
Posts: 1
Greetings all,
I am working on an application that currently unmashalls XML documents into Java objects using DOM -- i.e., it walks through the DOM nodes and builds a hierarchy of Java objects.
When I first heard about JAXB, I thought it might be a better choice than our current implementation. Rather than a bunch of tedious DOM calls, we could just define the appropriate mappings and let the JAXB framework handle it.
Upon closer inspection, however, I realized that JAXB can not unmarshall XML into instances of my existing Java classes. Unmarshalling only produces instances of JAXB-generated "content classes".
Granted, unmarshalling XML into JAXB content classes, and then mapping these content classes into my own classes, may be a little more elegant than our current method of just walking the DOM hierarchy. But it's not quite what I was hoping for.
It seems that there is a better XML - Java mapping tool called Quick, at Sourceforge. I wonder why JAXB doesn't offer any support for pre-existing classes, and whether they plan to in the future.
I agree. Here's the link:
subject: Serious JAXB Limitation?
It's not a secret anymore!