Hi,
> As far as the question that kicked of this discussion. If you
> do not need
> the any of the benefits of EJB then don't use it. However, I
> would recommend
> that you separate your data and business layers from your
> servlets and JSPs.
> Have them be presentation only. That way you could always
> grow into EJB
> without having to rewrite your front end.
Actually, we have done just this. Using the Struts framework, we have
JSP/Action classes that call upon "session" classes. These session classes
are our logic, which would become EJB. The action classes would then get the
EJB Home and do the EJB calling and so on. But the actual logic wouldn't
change..only the classes would have to extend EJB (or whatever it is they
extend) and stub/skeleton classes would be created.
