Ok, #2 would definitely explain why there's an EntityConverter and not an ObjectConverter. It seems there are, at the very least, three ways to approach this: 1. Do what I originally suggested (an "ObjectConverter" that serializes to the page scope), requiring objects to not be (or contain!) entity classes 2. Like #1, except instead requiring server-side state saving to be enabled (the default for Sun's JSF implementation it seems). 3. Like #1, except using the session scope and thus removing the limitations. Are there any drawbacks to caching in the session scope instead of the page scope? What're your thoughts? Any other options I'm missing? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4099038#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...