http://blog.jeffdouglas.com/2008/12/05/blazeds-referenceerror/?utm_source=rss&utm_medium=rss&utm_campaign=blazeds-referenceerror Get your head out of your #@! and into the clouds! Wed, 08 Feb 2012 07:57:55 +0000 hourly 1 http://wordpress.org/?v= http://blog.jeffdouglas.com/2008/12/05/blazeds-referenceerror/comment-page-1/#comment-75 Mike Wed, 21 Jan 2009 22:56:25 +0000 http://blog.jeffdouglas.com/?p=323#comment-75 I'm sure you've noticed by now, but in case you haven't, you don't need to make the fields in the Java object public, it works just like JSTL for getters and setters, so pojo.getName() would be serialized to to.name, not to.Name. There is a rule that Blaze will persist either public fields or those with public getters AND setters, so no read-only properties from the Java side. I’m sure you’ve noticed by now, but in case you haven’t, you don’t need to make the fields in the Java object public, it works just like JSTL for getters and setters, so pojo.getName() would be serialized to to.name, not to.Name. There is a rule that Blaze will persist either public fields or those with public getters AND setters, so no read-only properties from the Java side.

]]>