EJBs come in two flavours (as opposed to flavors), session beans and entity
beans.
Session beans represent business logic and rules, entity beans represent a
row in the database.
The model that you'd use is to have Actions do the basic processing of form
elements into data beans (just regular beans, nothing special), but no business
rules.
The Action then calls a session bean with the data bean to do something
(eg. usdate user details in the database). The session bean connects to the
database with an entity bean (or more than one depending on the database
structure).
Visually, you'd have
JSP => Action => Session Bean => Entity Bean => Database
Hope that helps.
At 06:37 AM 27/02/01 -0500, you wrote:
>
> I am in the process of convincing my company to go with MVC and Struts. As
> with any thing new, people are sometimes resistant
> to change. One of the opposition questions I am getting is, how will this
> work with EJB(problem is I don't know too much about EJB currently). Do the
> EJB's references just go in the Form and Action Bean and every thing else
> behaves the same? Are there any obvious points that I can bring up on the
> subject?
> Any help on this subject would be much appreciated!
>
> Thanks, Cameron Ingram
--
Kumera - a new Open Source Content Management System
for small to medium web sites written in Perl and using XML
http://www.cyber4.org/kumera/index.html
