0 Replies Latest reply on May 15, 2009 9:09 AM by ezanih

    Cannot see where Seam fits in between the UI, ESB and Backoffice layer

    ezanih
      Hi there

      I am trying to string together a neat little JEE proof-of-concept application beginning from the UI right up to the backend/backooffice and Oracle database.


      The simple stack is as follows (I wanna get this working first!)

      UI (Facelets/Richfaces) -->JMS Client-->Queue Listener-->ESB<--Queue Listener<--JMS Client<--Backoffice (JPA Entities, EJB3 Session Beans and MDBs, Oracle 10g DB)


      Once I get the simple stack working, I wanna add in jBPM and JRules as follows :-

      UI (Facelets/Richfaces)-->jBPM -->JMS Client-->Queue Listener-->ESB<--Queue Listener<--JMS Client<--Backoffice (JPA Entities, EJB3 Session Beans,JBoss Rules and MDBs, Oracle 10g DB)


      I'm a a little confused as I don't see where Seam fits in here. Should I create an EJB3 project or a Seam Web projection in my Eclipse IDE ? I know Enterprise Java Beans is a framework and Java Server Faces is a web framework. Seam is supposed to be a separate web framework that combines the two. How? Also how does Seam work in conjuction with the use of an Enterprise Service Bus to transport the serialized entity or session beans back and forth across the bus to and from the User Front End and the Backoffice where the business logic processing takes place?

      Isn't Seam suppose to use EJB3 as the backing bean, but what if the EJB3 session and JPA entity beans were transported across the bus ? What role would Seam have then ?


      Many thks!
      Ezani