Hmm... Not that simple all the time. The basic reasoning is of course correct but to achieve full use of the EJB/Servlet architecture one must add some elements. In my current architecture I add a layer between the entities and the servlet that I call "application facade". The application facade is (in case of a servlet-application, for an applet or application communicating through RMI there are other responisibilities) responsible for session-data management (ie. a SessionBean) and type-conversions between data-types from the servlet layer (typically simple serializable data like String and double) to the entity layer. In this way the servlet only propagates all the request data to the application facade which performs all application logic, often in a seemingly continous manner although it might be divided between many discontinous requests. So far it works pretty good! > It's actually pretty straightforward. The servlet acts as an EJB client; > it uses exactly the same API as all the other EJB client examples that are > floating around out there. Basically, you have a plain old servlet with > some plain old EJB client code embedded in it. There's nothing special you > need to do. �������������������������o unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
