<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Bill the Plumber</title>
	<atom:link href="http://bill.burkecentral.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://bill.burkecentral.com</link>
	<description>Software plumbing using middleware wrenches</description>
	<lastBuildDate>Mon, 23 Jan 2012 15:53:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on RESTEasy MOM: An exercise in JAX-RS RESTful WS design by javamonkey79</title>
		<link>http://bill.burkecentral.com/2008/06/16/resteasy-mom-an-exercise-in-jax-rs-restful-ws-design/#comment-4524</link>
		<dc:creator><![CDATA[javamonkey79]]></dc:creator>
		<pubDate>Mon, 23 Jan 2012 15:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=101#comment-4524</guid>
		<description><![CDATA[So if I read you right, it is possible to have only one MBR and MBW instead of one for each class in our DOM? If this is the case, then I wonder why this functionality isn&#039;t provided out of the box?

Restlet does have a JAX-RS implementation for the server side, but not the client side. That being said, I don&#039;t see the point. You don&#039;t get the dynamic path mapping that JAX-RS buys you.]]></description>
		<content:encoded><![CDATA[<p>So if I read you right, it is possible to have only one MBR and MBW instead of one for each class in our DOM? If this is the case, then I wonder why this functionality isn&#8217;t provided out of the box?</p>
<p>Restlet does have a JAX-RS implementation for the server side, but not the client side. That being said, I don&#8217;t see the point. You don&#8217;t get the dynamic path mapping that JAX-RS buys you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTEasy MOM: An exercise in JAX-RS RESTful WS design by billburke</title>
		<link>http://bill.burkecentral.com/2008/06/16/resteasy-mom-an-exercise-in-jax-rs-restful-ws-design/#comment-4523</link>
		<dc:creator><![CDATA[billburke]]></dc:creator>
		<pubDate>Mon, 23 Jan 2012 15:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=101#comment-4523</guid>
		<description><![CDATA[I don&#039;t know what your custom XML marshalling looks like or how it works, but MessageBodyReader/Writer can be tied to a specific mediatype via @Produces/Consumes annotations, also, look at the interface for MBR and MBW, you&#039;ll see isReadable, isWritable methods.  If you can easily match your custom classes using these methods, then there&#039;s no reason you can&#039;t have one MBR/MBW for your business logic.

I hate to correct you on the competition, but, I thought Restlet had a JAX-RS implementation?]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what your custom XML marshalling looks like or how it works, but MessageBodyReader/Writer can be tied to a specific mediatype via @Produces/Consumes annotations, also, look at the interface for MBR and MBW, you&#8217;ll see isReadable, isWritable methods.  If you can easily match your custom classes using these methods, then there&#8217;s no reason you can&#8217;t have one MBR/MBW for your business logic.</p>
<p>I hate to correct you on the competition, but, I thought Restlet had a JAX-RS implementation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTEasy MOM: An exercise in JAX-RS RESTful WS design by javamonkey79</title>
		<link>http://bill.burkecentral.com/2008/06/16/resteasy-mom-an-exercise-in-jax-rs-restful-ws-design/#comment-4522</link>
		<dc:creator><![CDATA[javamonkey79]]></dc:creator>
		<pubDate>Mon, 23 Jan 2012 15:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=101#comment-4522</guid>
		<description><![CDATA[We have a large in house library for our XML representation of our business logic. Something like:


   
      ...

This is a trivial representation. In reality there are hundreds of classes. 

So in order to make this work I would need to write a MessageBodyReader/Writer for every class? eg: foo, bar, baz, etc.? Or would it be possible to use reflection and only do this once for all of them? If reflection is possible, do you have any thoughts on why the library itself doesn&#039;t provide it?

I&#039;ve evaluated Restlet as well, and one of the things I really like about Restlet is that Object marshaling\unmarshaling is handled with no developer interaction - you just add XStream to you POM and it does the work for you. However, Restlet is not JAX-RS compliant.]]></description>
		<content:encoded><![CDATA[<p>We have a large in house library for our XML representation of our business logic. Something like:</p>
<p>      &#8230;</p>
<p>This is a trivial representation. In reality there are hundreds of classes. </p>
<p>So in order to make this work I would need to write a MessageBodyReader/Writer for every class? eg: foo, bar, baz, etc.? Or would it be possible to use reflection and only do this once for all of them? If reflection is possible, do you have any thoughts on why the library itself doesn&#8217;t provide it?</p>
<p>I&#8217;ve evaluated Restlet as well, and one of the things I really like about Restlet is that Object marshaling\unmarshaling is handled with no developer interaction &#8211; you just add XStream to you POM and it does the work for you. However, Restlet is not JAX-RS compliant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTEasy MOM: An exercise in JAX-RS RESTful WS design by billburke</title>
		<link>http://bill.burkecentral.com/2008/06/16/resteasy-mom-an-exercise-in-jax-rs-restful-ws-design/#comment-4521</link>
		<dc:creator><![CDATA[billburke]]></dc:creator>
		<pubDate>Mon, 23 Jan 2012 14:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=101#comment-4521</guid>
		<description><![CDATA[Not sure what your constraints are, but you could write your own MessageBodyReader/Writer for the types you need it done for.]]></description>
		<content:encoded><![CDATA[<p>Not sure what your constraints are, but you could write your own MessageBodyReader/Writer for the types you need it done for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RESTEasy MOM: An exercise in JAX-RS RESTful WS design by javamonkey79Shaun</title>
		<link>http://bill.burkecentral.com/2008/06/16/resteasy-mom-an-exercise-in-jax-rs-restful-ws-design/#comment-4520</link>
		<dc:creator><![CDATA[javamonkey79Shaun]]></dc:creator>
		<pubDate>Sat, 21 Jan 2012 01:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=101#comment-4520</guid>
		<description><![CDATA[How would use use JAX-RS if you can not apply JAXB to the objects you are passing over the wire? Is this possible?]]></description>
		<content:encoded><![CDATA[<p>How would use use JAX-RS if you can not apply JAXB to the objects you are passing over the wire? Is this possible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brainstorming REST Security Part I by billburke</title>
		<link>http://bill.burkecentral.com/2011/06/16/brainstorming-rest-security-part-i/#comment-4517</link>
		<dc:creator><![CDATA[billburke]]></dc:creator>
		<pubDate>Mon, 09 Jan 2012 14:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=535#comment-4517</guid>
		<description><![CDATA[I was brainstorming so take it as it is...Yes, use HTTPS, but I think digital signatures are better than passwords.  Why?  Well mainly because the server does not have to store passwords and just has to store a public key. So, if the server gets hacked, all the hacker gets is a bunch of information that is just public anyways.]]></description>
		<content:encoded><![CDATA[<p>I was brainstorming so take it as it is&#8230;Yes, use HTTPS, but I think digital signatures are better than passwords.  Why?  Well mainly because the server does not have to store passwords and just has to store a public key. So, if the server gets hacked, all the hacker gets is a bunch of information that is just public anyways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Brainstorming REST Security Part I by Larry</title>
		<link>http://bill.burkecentral.com/2011/06/16/brainstorming-rest-security-part-i/#comment-4516</link>
		<dc:creator><![CDATA[Larry]]></dc:creator>
		<pubDate>Sun, 08 Jan 2012 03:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=535#comment-4516</guid>
		<description><![CDATA[You recommend &quot;digitally signed requests&quot; for non-browser clients.  What if the client is passing sensitive information to a service?   Presumably you&#039;d want to use HTTPS to hide that sensitive information from eavesdropping.  Would you still recommend digital signatures in that situation as well as HTTPS, or just use something like HTTP basic authentication to verify the user?]]></description>
		<content:encoded><![CDATA[<p>You recommend &#8220;digitally signed requests&#8221; for non-browser clients.  What if the client is passing sensitive information to a service?   Presumably you&#8217;d want to use HTTPS to hide that sensitive information from eavesdropping.  Would you still recommend digital signatures in that situation as well as HTTPS, or just use something like HTTP basic authentication to verify the user?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Co-existence with Hibernate, JPA, and EJB3 by seetharam</title>
		<link>http://bill.burkecentral.com/2007/07/06/co-existence-with-hibernate-jpa-and-ejb3/#comment-4490</link>
		<dc:creator><![CDATA[seetharam]]></dc:creator>
		<pubDate>Tue, 06 Dec 2011 17:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://billburke.wordpress.com/2007/07/06/co-existence-with-hibernate-jpa-and-ejb3/#comment-4490</guid>
		<description><![CDATA[hi... greetings... 
its good.. about .. EJB  and Hibernate....
but.. you dint give... any... Exaple... on that..  for better.. understanding....]]></description>
		<content:encoded><![CDATA[<p>hi&#8230; greetings&#8230;<br />
its good.. about .. EJB  and Hibernate&#8230;.<br />
but.. you dint give&#8230; any&#8230; Exaple&#8230; on that..  for better.. understanding&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resteasy 2.3-RC1 Released, Please Testdrive! by Distributed Weekly 130 &#8212; Scott Banwart&#039;s Blog</title>
		<link>http://bill.burkecentral.com/2011/11/22/resteasy-2-3-rc1-released-please-testdrive/#comment-4480</link>
		<dc:creator><![CDATA[Distributed Weekly 130 &#8212; Scott Banwart&#039;s Blog]]></dc:creator>
		<pubDate>Fri, 25 Nov 2011 14:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=574#comment-4480</guid>
		<description><![CDATA[[...] Resteasy 2.3-RC1 Released, Please Testdrive!  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Resteasy 2.3-RC1 Released, Please Testdrive!  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resteasy 2.3-RC1 Released, Please Testdrive! by Stephane Epardaud</title>
		<link>http://bill.burkecentral.com/2011/11/22/resteasy-2-3-rc1-released-please-testdrive/#comment-4478</link>
		<dc:creator><![CDATA[Stephane Epardaud]]></dc:creator>
		<pubDate>Thu, 24 Nov 2011 14:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://bill.burkecentral.com/?p=574#comment-4478</guid>
		<description><![CDATA[GitHub: excellent news :)]]></description>
		<content:encoded><![CDATA[<p>GitHub: excellent news <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

