Hey
"William G. Thompson, Jr." wrote:
> > > The second decision is how to deal with the presentation layer. As has been said
> > > often here, JSPs are compiled into servlets, so there's nothing you can do with
> > > a JSP that you can't do with a servlet. But the advantage of JSPs is that they
> > > can be generated (using the right tools) by web designers with no programming
> > > skills. So you should give your web designers the advanced tools and use JSPs
> > > (plus of course pure HTML).
> >
> > An alternate opinion would be that giving web designers with no programming skills
> > tools that allow them to program is a bad idea. Personally, I prefer to completely
> > separate content from code. Using JSP causes this distinction to blur, and can
>result
> > in unmanagable and unmaintable websites.
This is somewhat untrue in JSP1.0 if the "use bean" tags are used. It is
even more untrue in JSP1.1 if taglibs are used. Complete
code/content/design separation can be done if JSP1.1 is used properly.
In the end it is not *what* you use but *how* you use it that really
matters. JSP is the most flexible dynamic content generation method I
know, and as such it allows you to totally screw things up, as well as
make absolutely beautiful designs. With a little thought it's not that
hard to achieve the latter.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
