The point of JAXB is to allow XML Schema files (.XSD files) to be "bound"
into classes that can, at runtime, be used to represent the structure
described in the Schema files. Additionally, the runtime classes can be
used to produce and read XML that conforms to the Schemas.
My point here is, the real benefit of JAXB (at least as far as I understand
it--JAXB Team, correct me if I'm wrong) is to be able to interpret XML
Schema into data structure. What the XML itself is used for (documents or
otherwise) is not really of interest to JAXB itself.
"Binding" in JAXB is about binding schemas into classes...NOT about
"binding" XML into runtime state. That is done after the binding process,
and is called marshalling/unmarshalling.
-Brandon Franklin
Thought River South
----- Original Message -----
From: "Pavel A. Sher" <pavel_at_actimind.com>
To: <JAXB-INTEREST_at_JAVA.SUN.COM>
Sent: Monday, May 12, 2003 11:02 PM
Subject: Document oriented XML Binding framework needed
> Hello,
>
> Is there any XML Binding framework which is able to correctly
> represent mixed content? I was tried two well-known frameworks: Sun
> JAXB and Castor. But both are seem to be data oriented frameworks. So
> my human-editable document with much mixed content will not be
> presented correctly.
>
> Maybe there are some other frameworks with document orientation as
> the implementation goal? Does the Sun plan to improve JAXB for
> support of document oriented XML?
>
> --
> Best regards,
> Pavel mailto:pavel_at_actimind.com
>