Mark A. Kolb wrote:
>
> Like yours, our team here has a group focused on presentation (HTML),
> and a group focused on back-end implementation (Java). We use JSP for
> dynamic content, and we don't put Java source code in our .jsp files.
>
I am just finishing up a medium-sized JSP 1.0-based application (about 20 pages,
but 100% dynamic and presented in six different languages). Even though I wrote it
all myself, I followed exactly this discipline -- business logic in servlets +
beans, and presentation logic in JSP. The point is that, even as the sole
developer, it is very empowering to know that you can play with the presentation
and not risk messing with your business logic code, and vice versa, due to the
separation. In addition, reuse of the business logic components is *much* easier
if there are no presentation details embedded in them.
The "benefits of separation" argument made sense when I first read about it ...
having just lived through a development project where the business logic was pretty
stable (a web-based transactional interface to a legacy application) but the
presentation went through several major evolutions, I can vouch for these benefits
from personal experience.
I did find myself having to write a little Java in my pages, but that was mostly
for things like loops. I'm looking forward to 1.1-based tag extensions, which will
eliminate the need for about 98% of my scriptlets.
Craig McClanahan
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
