Seam is a lot of infrastructure to add in as a base requirement, but it's oh so sweet to use. I think there's a lot of work to do regardless of seam or not in terms of JSF components. Seam does interesting things to expose things for you but leaves it up to you to do the rendering. Any JSF components built would be the same regardless as to whether this was a seam app or not. My hope over the past several months has been to gain insight into writing complex JSF components, and thus far I'm not particularly keen. There are a lot of rough edges throughout MyFaces and JSF. I've been trying to avoid creating yet another JSF framework for components, this seems outside the scope of jbpm. The alternative is tying ourselves to a specific implementation (MyFaces) and using their existing infrastructure(s) for things like external resource binding. How does everyone feel about an explicit tie to MyFaces? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961436#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...