On Sun, 28 Nov 1999, Tim Endres 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.
>
I'd have to agree with Tim here. I've seen large projects go into
super thrash mode while web designers cook up half baked presentation code.
Check out www.enhydra.com's XMLC technology for a great implementation of
Tim's idea.
Cheers,
Bill
> tim.
> Tim Endres - [EMAIL PROTECTED]
> ICE Engineering, Inc. - http://www.ice.com/
> "USENET - a slow moving self parody." - Peter Honeyman
>
> ===========================================================================
> 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".
>
===========================================================================
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".
