You can use any design pattern in your seam application, but you should be carefull with excessive bijection. Seam makes injection and outjection for each method you execute. So, if you make a Facade with lots of EAO injection you can slow your application. In my system i did some classes that i call BusinessRules(for some common rules in my system), EAO, Factory (using Seam Factories annotation) and my backing beans injecting only the necessary. I did a EJB project with all these classes and a war project with backing bean and web components.
Sry about english.
Hello Diego and Balvindar,
The following quote is from jsfcentral.com(Title is:David Geary discusses JSF, Ajax, and GWT)
Essentially that’s all you have, beans and views. Seam collapses all the traditional layers that you have to deal with like the DTO layer and the database layer. It collapses all those down essentially into just beans and views. On the other hand, it doesn’t prevent you from having those layers. If you want to have multiple layers you can do that, but by default we just have a very simple component model where we have beans and views, and it makes development much simpler with Seam, much easier to do
Diego,i wanted to avoid excessive bijection,but i got the error that i have described here:
(Please look at the last post)
Would you please describe more that what you did about avoiding excessive bijection?(Maybe with examples).