"mgrouch" wrote : EntityConverter and <s:convertEntity /> have serious limitation in both | Seam 2.0 and 1.2.1.GA - they require entity to be Seam managed. I hardly think this is a "serious limitation" - you are using Seam after all, and you'd be silly not to use a SMPC with Seam. Anyway, the main problem with this is that you cache every entity in the conversation scope (otherwise the entities become unmanaged) which is not too nice. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071212#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...