We just launched an Internet-based time and billing application on the web, using
JSP and servlets to connect to Enterprise JavaBeans. Follow the links to Timesolv
from http://www.elite.com/; registration is free. I'm a little too involved to be
unbiased, but it's the best JSP application I've seen yet.
Our best business case for JSP revolved around its flexibility. Most template
systems tend to limit your presentation to a very data-driven view; JSP is much
more flexible when it comes to integrating with advanced DHTML/JavaScript-based
interfaces.
Wes
Duffey Kevin wrote:
> Hi,
>
> I was wondering if anyone has JSP pages I can show my boss as a reference
> as to why we should be switching to the technology. He doesn't believe its
> a reliable solution at this time, and I want a way to show him some sites
> that are using it, besides giving him some info on its use and pros/cons.
>
> On that note, can anyone give me some tips on how I can prove its worth?
> Right now, we use .shtml pages, and we use a TemplateServlet that reads in
> .template files we create, replacing string tokens with dynamic content. I
> have already seen a 10x increase in speed in this manner on my local JSP
> site, using JavaBeans instead of this template servlet deal.
>
> Thanks.
>
> Kevin Duffey
> Software Engineer
> [EMAIL PROTECTED]
===========================================================================
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
