To implement a screen of the particular Use Case, the following artifacts should be created:
1. Action class handles logic of that particular screen, errors and, probably, validation. 2. ActionForm class stores and validates the data presented on the screen. 3. BusinessDelegate class is responsible for finding and performing inter-tier method call of the Stateless Session EJB fa�ade object that resides on the business tier. The value objects facilitate the interaction between BusinessDelegate and UseCase Fa�ade. See the description of Business Delegate pattern at http://developer.java.sun.com/developer/restricted/patterns/BusinessDelegate .html. See the description of ValueObject pattern at http://developer.java.sun.com/developer/restricted/patterns/ValueObject.html . 4. Use Case Fa�ade is Stateless Session EJB, which sits on the business tier and implements system-wise business methods that perform the logic of Use Case. See the Session Fa�ade pattern at http://developer.java.sun.com/developer/restricted/patterns/SessionFacade.ht ml 5. JSP Page represents view in the MVC pattern. It should contain only HTML code and all the logic should be encapsulated into the Struts JSP Tags. HTH ----- Original Message ----- From: "David Lauta" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, November 28, 2001 8:10 PM Subject: Misunderstood newbie > Hello, > > Can someone help me get started? > > Where/when is the proper place/time to create an ejb (Entity bean)? > Should I create access methods in the mapping class, > the form class or both or should I just create the objects > in the action class? > > I want to create a complex entry form that may create/update > three different tables in the database > > Say my JSP looks like: > > <H1> > ..... > </H1> > <HR> > <H2> > ..... > </H2> > <HR> > <H3> > ..... > </H3> > > The entry fields associated with H2 are directly related to H1 and > The entry fields associated with H3 are independant of H1 and H2 > > Is there a document that would outline the logic flows and database > interactions? > I first want to initialize H1 area stuff. > Based on user activity in H1 I want to then redisplay H1 and display H2 > The user is then expected to complete H3 > This would create/update an H1 entity bean > This would create/update an H2 entity bean > and create an H3 entity bean > > probably using three round trips to the JSP server. > > Any thoughts? > > -- > Thank you, > David Lauta > [EMAIL PROTECTED] > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
