<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: JAXB 2.0 doesn&#8217;t look so cool</title>
	<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/</link>
	<description>A weblog for Keith Lea and the Joust Project.</description>
	<pubDate>Fri, 12 Mar 2010 00:38:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: Phillip Tornroth</title>
		<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-2223</link>
		<pubDate>Wed, 03 May 2006 23:38:03 +0000</pubDate>
		<guid>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-2223</guid>
					<description>I've had the same issue with just about every piece of XML parsing code I've written, DOM/SAX/JAXB/Castor.. they're all obnoxious. It occured to me this week that the most freedom I've experienced peeling information out of XML has been when writing XSL documents, and that was because of XPath. I hooked up the JAXP XPath API's yesterday and wrote some code... I am sooo much more pleased with it than I've been with anything else. It's essentially still DOM code, but instead of walking the entire tree, you end up searching to get down the Node or NodeSet you want to deal with. For small parsing jobs, it's definitely the way I'm going from now on. I can send code if anyone's curious, but there are some examples floating about.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve had the same issue with just about every piece of XML parsing code I&#8217;ve written, DOM/SAX/JAXB/Castor.. they&#8217;re all obnoxious. It occured to me this week that the most freedom I&#8217;ve experienced peeling information out of XML has been when writing XSL documents, and that was because of XPath. I hooked up the JAXP XPath API&#8217;s yesterday and wrote some code&#8230; I am sooo much more pleased with it than I&#8217;ve been with anything else. It&#8217;s essentially still DOM code, but instead of walking the entire tree, you end up searching to get down the Node or NodeSet you want to deal with. For small parsing jobs, it&#8217;s definitely the way I&#8217;m going from now on. I can send code if anyone&#8217;s curious, but there are some examples floating about.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Xin Zhao</title>
		<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1942</link>
		<pubDate>Tue, 14 Mar 2006 14:04:10 +0000</pubDate>
		<guid>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1942</guid>
					<description>Try Liquid XML.</description>
		<content:encoded><![CDATA[<p>Try Liquid XML.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jos Dirksen</title>
		<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1941</link>
		<pubDate>Tue, 14 Mar 2006 12:22:24 +0000</pubDate>
		<guid>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1941</guid>
					<description>The tutorial you referenced doesn't seem to use jaxb 2.0, but JAXB 1.0.5. From the release notes of JAXB2.0 apparently the number of classes generated is significantly reduced and the jars you need to include also seem to made smaller.

You might try that version before going back to dom...</description>
		<content:encoded><![CDATA[<p>The tutorial you referenced doesn&#8217;t seem to use jaxb 2.0, but JAXB 1.0.5. From the release notes of JAXB2.0 apparently the number of classes generated is significantly reduced and the jars you need to include also seem to made smaller.</p>
<p>You might try that version before going back to dom&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Doug</title>
		<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1939</link>
		<pubDate>Tue, 14 Mar 2006 03:08:24 +0000</pubDate>
		<guid>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1939</guid>
					<description>Take a look at the Castor project. It's much simpler to learn and use than JAXB and still quite powerful. Worth a look.

There are a couple of other libraries that are similar whose names I can't remember. One is at Apache, XML Beans I think.

Doug</description>
		<content:encoded><![CDATA[<p>Take a look at the Castor project. It&#8217;s much simpler to learn and use than JAXB and still quite powerful. Worth a look.</p>
<p>There are a couple of other libraries that are similar whose names I can&#8217;t remember. One is at Apache, XML Beans I think.</p>
<p>Doug
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Charlie Hayes</title>
		<link>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1938</link>
		<pubDate>Tue, 14 Mar 2006 01:40:58 +0000</pubDate>
		<guid>http://joust.kano.net/weblog/archive/2006/03/13/jaxb-20-doesnt-look-so-cool/#comment-1938</guid>
					<description>Wow, thats crazy! 45 classes is insane.</description>
		<content:encoded><![CDATA[<p>Wow, thats crazy! 45 classes is insane.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
