Hi, I think EJB's should handle the business logic part of the app and a standard web-application the front-end. That said code the businnes-logic as if it were running without knowing what frontend could be using it. This results in a (front-end view) black box that does something. To scale up to EJB you could jst change the inner-workings of the black-box and the front-end would notice nothing.
Something that works like this is Jyve. It worked (when I looked at it) with model-1-JSP's and a single backend-class. It took me very little time to put a model-2 frontend in front of it. And in a second step (to evaluate it) I threw a Struts frontend to it... The backend never changed. Keeping the same backend-class-interface it would be possible to use EJB's in the backend-class... hope this helps Alexander -----Original Message----- From: Peter Georgiou [mailto:[EMAIL PROTECTED]] Sent: Monday, January 21, 2002 1:23 PM To: Struts Users Mailing List Subject: scaling up a strurt app to use ejb Hi I'm developing a struts app at the moment using Resin as my JSP engine. I realise its probably overkill to use EJBs right now. However, there may come a time when I need to scale up to a distributed architecture. My question is: how easy/difficult is it to scale my stuts app up to something that uses EJBs? I'd like to make the code I'm writing now in a way which makes it is painless as possible when it comes changing over to a distributed architecture. I'd also like to stick with Resin, which I think is a nice product. How does Resin's implementation of using distributed object compare with other products? Thanks Peter -- 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]>
