You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlbeans-user@xml.apache.org by Martin Wegner <ma...@yahoo.com> on 2004/07/23 16:53:49 UTC
JAXB and XMLBeans Best Practicies
Folks,
Brett McLaughlin wrote up the new Apache implementation of JAXB, JaxMe:
http://www-106.ibm.com/developerworks/xml/library/x-pracdb4/?ca=dnt-528
This brought up a discussion around here about the strengths and
weaknesses of both JAXB and XMLBeans. What this discussion brought out
was that "best practices" of JAXB and XMLBeans are still rather cloudy.
So I would like to solicit this group on what they have found to be the
situations where XMLBeans works (and does not work) and the same for JAXB
(assuming you came to XMLBeans from having found Castor/JAXB lacking in
some form).
Thanks.
--Marty
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-user-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
RE: JAXB and XMLBeans Best Practicies
Posted by Shmuel Koller <sh...@netvision.net.il>.
Do you mean JAXB reference implementation ?
If yes - I think it is not W3C schema compliant, and nowadays this is a
minimal/entry requirement. Even Castor is not compliant.
Do you mean JAXB APIs and specs ?
If yes - may be XMLBeans is JAXB compliant, or plans to be.
Personally - I do not think there is anything coming close to XMLBeans.
It has multiple LIVE models at run time, Eclipse feature or plans, affinity
to
Web Services XML, just from memory.
I do not know JaxMe - but see room for combined effort within Apache
to emmit all good things via one and only one strategic Java-XML binding
tool.
Multiple tools is just fine, but one tool with all goodies -
will strenghten Java open source market - by creating de-facto standard
engines
(like XERCES) - instead of endless comparisions.
Shmuel Koller
-----Original Message-----
From: Martin Wegner [mailto:marty_wegner@yahoo.com]
Sent: ?a 23 eaie 2004 16:54?
To: xmlbeans-user@xml.apache.org
Subject: JAXB and XMLBeans Best Practicies
Folks,
Brett McLaughlin wrote up the new Apache implementation of JAXB, JaxMe:
http://www-106.ibm.com/developerworks/xml/library/x-pracdb4/?ca=dnt-528
This brought up a discussion around here about the strengths and
weaknesses of both JAXB and XMLBeans. What this discussion brought out
was that "best practices" of JAXB and XMLBeans are still rather cloudy.
So I would like to solicit this group on what they have found to be the
situations where XMLBeans works (and does not work) and the same for JAXB
(assuming you came to XMLBeans from having found Castor/JAXB lacking in
some form).
Thanks.
--Marty
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-user-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-user-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
RE: JAXB and XMLBeans Best Practicies
Posted by Shmuel Koller <sh...@netvision.net.il>.
Do you mean JAXB reference implementation ?
If yes - I think it is not W3C schema compliant, and nowadays this is a
minimal/entry requirement. Even Castor is not compliant.
Do you mean JAXB APIs and specs ?
If yes - may be XMLBeans is JAXB compliant, or plans to be.
Personally - I do not think there is anything coming close to XMLBeans.
It has multiple LIVE models at run time, Eclipse feature or plans, affinity
to
Web Services XML, just from memory.
I do not know JaxMe - but see room for combined effort within Apache
to emmit all good things via one and only one strategic Java-XML binding
tool.
Multiple tools is just fine, but one tool with all goodies -
will strenghten Java open source market - by creating de-facto standard
engines
(like XERCES) - instead of endless comparisions.
Shmuel Koller
-----Original Message-----
From: Martin Wegner [mailto:marty_wegner@yahoo.com]
Sent: ?a 23 eaie 2004 16:54?
To: xmlbeans-user@xml.apache.org
Subject: JAXB and XMLBeans Best Practicies
Folks,
Brett McLaughlin wrote up the new Apache implementation of JAXB, JaxMe:
http://www-106.ibm.com/developerworks/xml/library/x-pracdb4/?ca=dnt-528
This brought up a discussion around here about the strengths and
weaknesses of both JAXB and XMLBeans. What this discussion brought out
was that "best practices" of JAXB and XMLBeans are still rather cloudy.
So I would like to solicit this group on what they have found to be the
situations where XMLBeans works (and does not work) and the same for JAXB
(assuming you came to XMLBeans from having found Castor/JAXB lacking in
some form).
Thanks.
--Marty
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-user-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
- ---------------------------------------------------------------------
To unsubscribe, e-mail: xmlbeans-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-user-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/