tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig R. McClanahan" <>
Subject RE: comparison between SERVLET/JSP to Cold Fusion
Date Thu, 01 Nov 2001 16:38:39 GMT

On Thu, 1 Nov 2001, Henry wrote:

> Date: Thu, 1 Nov 2001 09:10:30 -0700 (Mountain Standard Time)
> From: Henry <>
> Reply-To: Tomcat Users List <>
> To: Tomcat Users List <>
> Subject: RE: comparison between SERVLET/JSP to Cold Fusion
> Then is there any existing tag library developed for easy
> database IO?  and tools that bound java beans to databases
> (not to mention EJB, it can't be used in jsp as  <jsp:usebean ...> which
> will not be useful in developing a pure database website
> FAST enough).

Why can't you use EJBs?  If they have method signatures that correspond to
JavaBeans properties, they are certainly usable (although you might have
performance issues if the actual EJB is on a different server - there are
good design patterns to deal with this sort of thing).

> also I see that use input in the form of "text", "checkbox", can all
> be saved in a bean in a JSP without any    "getParameter()"
> and any "bean.setValue(...)".  why there can't be a feature to
> set "text", "checkbox" by providing a bean in a JSP?

This is one of the problems that web applications frameworks like Struts
( solves for you -- it includes a rich
custom tag library that makes keeping track of input field contents (and
redisplaying them when a validation error fails) pretty painless.

I also encourage you to do some studying on appropriate design patterns
for web applications built with servlets and JSPs.  Rapid development is
certainly one goal, but building an application that can be maintained and
enhanced later (as well as scales in performance) is also important to
most users.

A book that is on my bookshelf (except when I'm writing an app, where it
is sitting open on my desk :-) is "Core J2EE Patterns" by Deepak Alur,
John Crupi, and Dan Malks.  It is a tremendously useful catalog of design
patterns -- not only for new apps, but also for consideration when
refactoring old ones.


To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message