anonymous wrote : You ignore the fact that JSF knowledge is much wider spread. Which means that buiding the site in JSF makes it easer for us to deliver JSF components which will be an interesting asset for our project. Also JSF related expertise is easier to find/get/manage. I absolutely agree with that statement! I see JSF Knowledge growing everywhere, and it makes sense, it is a Java EE 5 standard! By the way, JSF is a full day in the JBoss and EJB 3 Training, so it should be a direction JBoss is going... And the approach started with the current console (providing facelets for reusable components) is perfectly the right one I would say. And currently there is some effort going on to integrate JSF applications into portals as portlets (again standards everywhere!), so I think this will make it easy for customers to leverage the console also as starting point for own web guis.... Since EJB3 seems to be seen as too limiting, I would vote for POJO + JPA. In the implementation, this can be also annotated to be a EJB3 app if the container supports it (at least it works in my mind at the moment ;-)). Cheers Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140067#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...