Hi sdheepa ,
One As JSP is multithreaded the useage of servlets for multithreading is
redundant.
you are actually calling one more program, i see no advantage as a JSP is
converted to a servlet at the server side.
two, the architecture of EJB does specify the useage of beans, it is a sun
ceritifed architecture, and can be used w/o apprehentions
JSP->bean->EJB
this architecture, is highly scalable and performace capacity is very good,
as my current project is doing this, i can vouch for it.
Regards
Amit
> -----Original Message-----
> From: sdheepa [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 24, 1999 4:05 PM
> To: [EMAIL PROTECTED]
> Subject: Which Architecture..?
>
> Just look at the Foll. Architecture:
>
> JSP File ->Contacting Servlet-> This Servlet in
> turn talks with EJB to perform bussiness logic...
>
> What are the advantages/diadvantages of having the
> Servlet to contact the EJB..with repect to performance
> and scalability...
>
> Instead of having the servlet contact the EJB why not
> we have the Java Bean talk to the EJB..
>
> ie what problems we might face if the architecture is
> like this:
> JSP File ->Contacting Java Bean-> This Bean in turn
> talks with EJB to perform bussiness logic...
>
> Other than multi-threading do we have any other
> addtional adv. if we use Servlets..?
>
> Can someone help me..?
>
> Thanks in advance..
> Dheepa
>
> ==========================================================================
> =
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
