Comments on: XML Binding Framework Beta-1 Released http://chaoticjava.com/posts/xml-binding-framework-beta-1-released/ The internet, design patterns, frameworks and Java Sat, 05 Nov 2011 18:39:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Avah http://chaoticjava.com/posts/xml-binding-framework-beta-1-released/comment-page-1/#comment-125 Avah Mon, 16 Jan 2006 05:36:36 +0000 http://javachaos.crazyredpanda.com/?p=87#comment-125 Well, Geoffrey, I have <a href="http://chaoticjava.com/?p=51" rel="nofollow">written about it before</a>, and I'm willing to reiterate. X2J is doing both <i>reliable serialization</i> and <i>transparent XML binding</i>. <b>Reliable serialization</b> means (for me): * a serialization that when deserialized, the object tree looks the same as when it was serialized. * a serialization where the resulting XML is readable by any application and does not even resemble proprietary serialization mechanisms. <b>Transparent XML binding</b> means (again, for me): * a binding where you use your Own objects, and not generated objects, for the binding. * a binding where no external configuration is needed, <i>specifically</i> XML Schema Definions. This gives you the following advantages over other frameworks, methinks: * <b>No need for long XSD files.</b> I've heard some people claiming they aren't well enough into XSD because they've written <i>only</i> three pages of XSD for their application. These files are unmaintainable, unreadable and certainly cause a lot of problem in any application. * <b>No need to fear for your serialized data.</b> What you serialize today you can deserialize tomorrow with anything you'd want - X2J will even generate an XSD for you if you choose to do your deserialization without X2J (suppose on a different language-platform.) * <b>You can start using X2J from the start, middle or end.</b> Either generate X2J classes from an XSD schema and scrap that horrible thing for heaven's come, or start annotating your beans today: Your XML is still the same XML, and with simple annotations with similar names to what you've come to know in the Schema files, annotations <i>are</i> easy. And even more extensive than you'd expect. Obviously, not all features discussed here are in the current beta (for example, XSD generation) but they're going in there before the release. If you want, I'm willing to have an open conversation about the subject. Well, Geoffrey, I have written about it before, and I’m willing to reiterate.

X2J is doing both reliable serialization and transparent XML binding.

Reliable serialization means (for me):

* a serialization that when deserialized, the object tree looks the same as when it was serialized.
* a serialization where the resulting XML is readable by any application and does not even resemble proprietary serialization mechanisms.

Transparent XML binding means (again, for me):

* a binding where you use your Own objects, and not generated objects, for the binding.
* a binding where no external configuration is needed, specifically XML Schema Definions.

This gives you the following advantages over other frameworks, methinks:

* No need for long XSD files. I’ve heard some people claiming they aren’t well enough into XSD because they’ve written only three pages of XSD for their application. These files are unmaintainable, unreadable and certainly cause a lot of problem in any application.
* No need to fear for your serialized data. What you serialize today you can deserialize tomorrow with anything you’d want – X2J will even generate an XSD for you if you choose to do your deserialization without X2J (suppose on a different language-platform.)
* You can start using X2J from the start, middle or end. Either generate X2J classes from an XSD schema and scrap that horrible thing for heaven’s come, or start annotating your beans today: Your XML is still the same XML, and with simple annotations with similar names to what you’ve come to know in the Schema files, annotations are easy. And even more extensive than you’d expect.

Obviously, not all features discussed here are in the current beta (for example, XSD generation) but they’re going in there before the release.

If you want, I’m willing to have an open conversation about the subject.

]]> By: Geoffrey http://chaoticjava.com/posts/xml-binding-framework-beta-1-released/comment-page-1/#comment-124 Geoffrey Mon, 16 Jan 2006 01:13:06 +0000 http://javachaos.crazyredpanda.com/?p=87#comment-124 So how does X2J stack up against other XML binding frameworks? What advantages does it bring to the table? Why another framework? So how does X2J stack up against other XML binding frameworks? What advantages does it bring to the table? Why another framework?

]]> By: Avah http://chaoticjava.com/posts/xml-binding-framework-beta-1-released/comment-page-1/#comment-122 Avah Sat, 14 Jan 2006 19:14:00 +0000 http://javachaos.crazyredpanda.com/?p=87#comment-122 It's okay to download the .jar file now, it contains the class files. However, remember that you need to download the dependencies stated in my previous comment! It’s okay to download the .jar file now, it contains the class files. However, remember that you need to download the dependencies stated in my previous comment!

]]> By: Avah http://chaoticjava.com/posts/xml-binding-framework-beta-1-released/comment-page-1/#comment-121 Avah Sat, 14 Jan 2006 18:42:06 +0000 http://javachaos.crazyredpanda.com/?p=87#comment-121 First bug: .jar file was packaged with source files and not class files. Oops. :) Hope to fix this before anyone notices, but if you Do notice, be aware that you should download the sources in the .tar.gz file and that you need the <i>resolver.jar</i>, <i>xercesimpl.jar</i> and <i>xml-apis.jar</i> .jar files from <a href="http://xml.apache.org/xalan-j/downloads.html" rel="nofollow">Xalan-J</a> for this to compile. I will get an Ant build script attached with the sources next time. Sorry! First bug: .jar file was packaged with source files and not class files. Oops. :)

Hope to fix this before anyone notices, but if you Do notice, be aware that you should download the sources in the .tar.gz file and that you need the resolver.jar, xercesimpl.jar and xml-apis.jar .jar files from Xalan-J for this to compile.

I will get an Ant build script attached with the sources next time. Sorry!

]]>