<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Performance tests for introspection of JavaBeans</title>
	<atom:link href="http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/</link>
	<description>Writing about my experiences with technology and all different kinds of projects and experiments</description>
	<pubDate>Thu, 04 Dec 2008 03:52:55 +0000</pubDate>
	
		<item>
		<title>By: Christian Schenk</title>
		<link>http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-465</link>
		<dc:creator>Christian Schenk</dc:creator>
		<pubDate>Sun, 02 Dec 2007 15:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-465</guid>
		<description>As a follow up to my tests with the Introspector from the Java API, I did some more testing with various Java Bean to Java Bean mappers. Have a look at it &lt;a href="http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/" rel="nofollow"&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>As a follow up to my tests with the Introspector from the Java API, I did some more testing with various Java Bean to Java Bean mappers. Have a look at it <a href="http://www.christianschenk.org/blog/java-bean-mapper-performance-tests/">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Schenk</title>
		<link>http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-94</link>
		<dc:creator>Christian Schenk</dc:creator>
		<pubDate>Sat, 11 Aug 2007 16:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-94</guid>
		<description>Hi Simon,

thank you for the link to &lt;a title="Dozer" href="http://dozer.sourceforge.net"&gt;Dozer&lt;/a&gt;. I'll check it out and write a (hopefully detailed) post soon.

I obviously forgot to upload the test code: now you can have a look at it &lt;a href="http://data.christianschenk.org/performance-tests-for-introspection-of-javabeans/xref/org/christianschenk/beanintrospect/PerformanceComparison.html"&gt;here&lt;/a&gt;. Basically it's a "big for loop" and certainly not the most realistic way to test this, but I think that it gives us a good indication for the one or the other solution - whether this might be faster than that and so on.

Do you have another idea for a performance test - instead of the "big for loop"?</description>
		<content:encoded><![CDATA[<p>Hi Simon,</p>
<p>thank you for the link to <a title="Dozer" href="http://dozer.sourceforge.net">Dozer</a>. I&#8217;ll check it out and write a (hopefully detailed) post soon.</p>
<p>I obviously forgot to upload the test code: now you can have a look at it <a href="http://data.christianschenk.org/performance-tests-for-introspection-of-javabeans/xref/org/christianschenk/beanintrospect/PerformanceComparison.html">here</a>. Basically it&#8217;s a &#8220;big for loop&#8221; and certainly not the most realistic way to test this, but I think that it gives us a good indication for the one or the other solution - whether this might be faster than that and so on.</p>
<p>Do you have another idea for a performance test - instead of the &#8220;big for loop&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Lebettre</title>
		<link>http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-93</link>
		<dc:creator>Simon Lebettre</dc:creator>
		<pubDate>Fri, 10 Aug 2007 15:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.christianschenk.org/blog/performance-tests-for-introspection-of-javabeans/#comment-93</guid>
		<description>Hi, facing exactly the same problem (having to write an enormous load of boring code to map from JAXB objects to business DTOs), I found this framework : http://dozer.sourceforge.net

In my own performance tests (real use on the server with logs), i see the mapping (after the first time it encounters a new object wich caches all the methods lookups) is taking 0 ms , whenever I use hand coded mapping or dozer. 

By the way , I figured that for this matter, testing in a big for loop on my dev computer makes no sense, I think I end up testing what my operating system is doing!

- Could you try your perf test with dozer  ?
- Could you explain your performance tests methodology / provide the test code ?</description>
		<content:encoded><![CDATA[<p>Hi, facing exactly the same problem (having to write an enormous load of boring code to map from JAXB objects to business DTOs), I found this framework : <a href="http://dozer.sourceforge.net">http://dozer.sourceforge.net</a></p>
<p>In my own performance tests (real use on the server with logs), i see the mapping (after the first time it encounters a new object wich caches all the methods lookups) is taking 0 ms , whenever I use hand coded mapping or dozer. </p>
<p>By the way , I figured that for this matter, testing in a big for loop on my dev computer makes no sense, I think I end up testing what my operating system is doing!</p>
<p>- Could you try your perf test with dozer  ?<br />
- Could you explain your performance tests methodology / provide the test code ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
