Hi, What are the strategy/patterns proposed by Jboss Seam to link Seam framework with a service layer ?
Most of the frameworks like Struts, Seam, ... propose solutions to facilitate the work of the web designer, web developer but they don't present anything concerning the strategy to adopt in order to integrate the actions with service layer. The action is not at all the right place where to put the business logic. For the Struts world, appfuse has been an interesting example where such a strategy was presented but for Seam ... Remarks : - What I mean by service layer are java classes where the business logic is defined. These java classes will contain methods like "calculateFee", "changeOrderStatus". - Maybe, this is a chapter that should be added in the future in the Seam documentation - Most of the examples presented in the JBOSS-SEAM-2.0.0.GA took the assumption that the data will be updated from POJO but I'm not sure at all that such approach is tolerated in enterprise world where DAO pattern must be used Regards, Charles View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128350#4128350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128350 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
