hello all,
someone was mentioning about keeping the business logic in EJB or
SERVLET , could someone explain more about where to keep the logic to be
efficient enough.
i think craig was saying something about having a single servlet for
the entire appln and that servlet routes the request to the ejb which is
having the business logic, why can't we have the business logic in the
servlet itself.
please explain..
thanx in advance.
aciteam
> ----------
> From: Chris Macias[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Monday, October 25, 1999 10:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: when to use Bean !!!
>
> Craig,
>
> A polite way of saying "RTFM", huh? :-)
>
> What you didn't say (but could have) is that this is a JSP-specific
> interest list, and the questions we're asking are really drifting across
> the line from "JSP" to "Web application architecture". One of the many
> growing pains of learning new technologies: figuring out where to ask your
> questions.
>
>
> Tom and Jeff,
>
> Thanks to both of you for the feedback. I'd like to ask a (brief) follow
> up
> question or three, and the guys who posted before me may as well, but I
> wonder there is a more appropriate list we could move the thread to. Maybe
> there's a "J2EE" list out there, one the covers the spectrum of
> server-side
> Java technologies and how best to fit the pieces together. Anybody know if
> this exists?
>
> Christopher
>
> -----Original Message-----
> From: Craig McClanahan [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, October 25, 1999 11:05 AM
> To: [EMAIL PROTECTED]
> Subject: Re: when to use Bean !!!
>
> Chris Macias wrote:
>
> > ...and this could probably be expanded to "When to use a servlet and
> when
> > to use a Bean and when to use an EJB", but now we're asking for a white
> > paper! :-)
> >
> > But, seriously, can any of the gurus out there help out us newbies with
> > some 'rules of thumb' for when to use which technology? Rough guesses
> and
> > half-formed opinions welcome. It's more than we have now!
> >
>
> And don't forget to ask about how mail, directory servers, messaging, and
> database
> access fit in to the web application model as well :-).
>
> A pretty good set of documentation that includes answers to these
> questions, at
> various levels of detail, is in the Java2 Enterprise Edition (J2EE) pages
> on the
> JavaSoft web site.
>
> http://java.sun.com/j2ee
>
> I would start with the Overview and the associated white papers for
> introductory
> information. For servlet and JSP developers, the Application Programming
> Model
> manual includes some pretty comprehensive advice and examples of how this
> all fits
> together. There's also a sample application to illustrate the suggested
> principles.
>
> Craig McClanahan
>
> ==========================================================================
> =
> 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
>
===========================================================================
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
