jsp/servlet? EJB?

[Vishal Soni]

Hi,
I am in the planning phase for a new ecommerce project. I am currently in the process of deciding whether to use a jsp/servlet centric approach or go for EJB. It is not clear at this point whether the application would need the kind of scalability, distributed nature, method-level security as EJB promises but things may change and all of the above may become necessary. I am in a fix whether to go ahead with an EJB-based approach and bear the performance overheads right now or come up with a jsp/servlet approach. Is there a way in which I can avoid EJB at this point but in case requirement arises, I can switch to it very easily? If yes, how should I go about it?
Thanks in advance,
cheers,
vishal

[Chris Mathews]

If you utilize Business Delegates to perform all business operations then you will be leaving yourself with the desired flexibility.
Typically in an EJB Application Business Delegates will be used to hide the complexity of getting the initial context, looking up the home interface, retrieving a reference to a remote object, and handling exceptions. It goes a long way to decoupling your clients from the business components. In your case the business delegates could just hide the access of DAO objects. If you later feel the need to go with EJB then only the Business Delegates will need to change, the client interface can remain the same.
That is my suggestion.
Here is an online reference to the Business Delegate Pattern.
[ October 21, 2002: Message edited by: Chris Mathews ]

[Simon Brown]

... yes, and don't forget your value objects.
Simon