Hi! I agree that configuration is boring.... (that is one of the reasons I think Seam could be more productive than Spring), but after years of development, I feel uneasy to use a technology if I don't feel that I can go somewhere and read a good "map" of "how to deal with the configuration stuff by hand"... I know that the new trend is to imitate "Ruby on Rails" and have scaffolding and convention over configuration... and that... is great for new projects... but in my experience... one has to deal alot with existing projects, existing configuration, existing application servers... one of the reasons I love hibernate is because it "plays well with others", I can map my POJO to pretty much any old and badly designed database... I like Spring because I can be used pretty much anywhere... And I like Seam... because I just love the bijection idea... and the fact that I can "configure" it with almost no XML (unlike spring) I was ready to accept the fact that Seam is for EE5 or later versions (so it won't run everywhere), but then I read that I can be run in tomcat... so... if it can run in tomcat... it should be posible to use it pretty much in any container (as long as it runs in JDK1.5 or later), but I feel that an example showing how to do that, step by step, is just missing... I do believe that one of Seam advantages is that "configuration" is not as verbose as in Spring... but it while it is less verbose... it is either more complex... or less explained... Convention over configuration is a good idea... but only if that convention is clearly documented... and if configuration can be enabled for special (or not so special) cases... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4044285#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...