4 Replies Latest reply on Sep 29, 2009 11:21 PM by Jeremy Spring

    business slash service layer best practice

    Jeremy Spring Newbie

      What is the Seam best practice for using a business / service layer in between my action session bean and my EJBs that use PersistenceContext in the DAO layer?


      I have a significant amount of data processing to do after retrieving data and before handing it back to the session bean.  I know seam was designed to eliminate the need for a business layer however the session bean would be unnecessarily large otherwise.  I have tried using a Java Bean class as well as a separate Session bean class for this purpose but am having difficulty wiring components together.