Here you go:
Struts: http://jakarta.apache.org/struts
Xalan: http://xml.apache.org/xalan
I'm pretty sure those are right, but the Apache site seems to be down right
now, so I can't check.
--
Martin Cooper
Tumbleweed Communications
----- Original Message -----
From: "Neal Cabage" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 30, 2000 1:50 PM
Subject: Re: Servlets v. JSP
> Hey - thanks for the info. Yeah, someone else also mentioned Struts to me
> recently; I'll look into it. BTW, you mentioned Xalan XSL parser. Could
> you tell me where I could get that? I'm using JRUN as my app server and i
> *SWARE* the damned tag for parsing XSL doesn't work!
>
> Thanks.
> Neal
>
> -----Original Message-----
> From: A mailing list about Java Server Pages specification and reference
> [mailto:[EMAIL PROTECTED]]On Behalf Of Duffey, Kevin
> Sent: Saturday, December 30, 2000 6:12 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JSP-INTEREST] Servlets v. JSP
>
>
> I beg to differ. JSP pages can often be converted to more optimized
servlets
> than hand-coding the servlet yourself. This depends on the author of the
JSP
> engine that does the conversion of the JSP page, but in general there are
> some advantages to using JSP. However, I a strong advocate for the MVC
> model. Frameworks like Struts allow more separation of the Model, View and
> Controller. By using Struts or frameworks like it, you use JSP pages
almost
> exclusively for HTML content, with some dynamic Java code embeded to do
> looping or conditional displays of html. With JSP 1.1, its better to use a
> tag-lib to remove as much java code out of a jsp page as possible. As I
> discovered, if your using servlets to do html, you have hard-coded html
that
> is a pain in the ass to modify (for the most part). Worse, if you utilize
a
> hierachy of servlets, where a base servlet may display a few items with
some
> hooks in it to call descendant servlet methods to add more content, its
much
> harder to make a change without affecting other areas of the site.
>
> Something I am looking in to is instead of JSP with html, using JSP to
> return dynamic XML, which then passes through Xalan XSLT engine to convert
> it to HTML via XSL. While its an extra step, and does indeed cost in
> performance, you can always add more hardware. That is afterall one of the
> benefits of moving to an application server that supports load balancing
and
> fail-over. You simply add in another server and you can handle "x" more
> hits, as well as achieve a little more fail-over safety of your site. This
> does depend on the mechanism an app server uses to fail over to other
> servers. WebLogic has a "buddy" system, where it fails over to one other
> server, so any session data in memory on one server is replicated to the
> second server as well (therefore increasing the amount of memory needed
for
> each server). Orion app server does it a bit differently, with the use of
> island clusters. Each server in an island shares its memory with the other
> servers. If you have 10 servers in one island, all 10 servers share any
> memory objects in their ServletContext with the other servers on the
island,
> thus requiring huge amounts of memory for each server (assuming each
client
> on each server uses a lot of memory). However, a benefit is that you can
> just put two or three servers in each island, and have several islands
> instead!
>
> Anyways..for what its worth, I would look into Struts or similar
frameworks.
> They provide the best of all worlds..use of JSP for the View, Servlets for
> controlling the flow, and the ability to call EJB or other session classes
> to do the business logic, thus separating the control into two areas of
more
> manageable chunks.
>
>
> > -----Original Message-----
> > From: Fetyko Jan [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, December 30, 2000 11:23 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Servlets v. JSP
> >
> >
> > One of the good reasons is that the servlet is faster then a JSP page.
> > If you get 1000's hits per hour to the same URL, you want it
> > to be fast.
> > Another reason might be that with building servlets you're
> > separating the
> > presentation layer from the processing layer.
> >
> > Jf
> >
> >
> >
> >
> > Neal Cabage
> > <ncabage@ICONIXX. To:
> > [EMAIL PROTECTED]
> > COM> cc:
> > Sent by: A Subject:
> > Servlets v. JSP
> > mailing list
> > about Java Server
> > Pages
> > specification and
> > reference
> > <JSP-INTEREST@jav
> > a.sun.com>
> >
> >
> > 12/29/00 06:59 PM
> > Please respond to
> > nealcabage
> >
> >
> >
> >
> >
> >
> > Anyone out there using servlets rather than JSPs? Why would
> > a person build
> > a servlet rather than letting JSP just build one for you. My initial
> > thought is that a pure hand-written servlet might be more efficient if
> > there
> > is no actual output. Perhaps one might also consider it
> > better style for
> > the same reason. This is just speculation however and JSP just seems
> > easier
> > and more time efficient...so would there be a good reason for
> > hand-writing
> > your own servlets instead?
> >
> > Thanks.
> > Neal
> >
> > ==============================================================
> > =============
> > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> > JSP-INTEREST".
> > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
> > DIGEST".
> > Some relevant FAQs on JSP/Servlets can be found at:
> >
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
> >
> > ==============================================================
> > =============
> > To unsubscribe: mailto [EMAIL PROTECTED] with body:
> > "signoff JSP-INTEREST".
> > For digest: mailto [EMAIL PROTECTED] with body: "set
> > JSP-INTEREST DIGEST".
> > Some relevant FAQs on JSP/Servlets can be found at:
> >
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
> >
>
>
===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
> DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
>
===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
> For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
