> -----Original Message-----
> From: Andrew S Tomlinson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 09, 2000 9:17 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Model 2 & 3 Architecture
>
> 3. building XSL files is a radically different proposition to
> building HTML
> (and by extension JSP). This means that you lose the
> *division of labour*
> that assigns UI construction to (presumably less *technical*)
> Web Designers.
> Again I have found this to be the case for anything other
> than the most
> trivial of cases.
>
> How does this compare to others' experiences?
This is a very important point for developers in shops like mine where we
break down the development of a project to different units. Our Creative
department meets with the customer and hammers out the "look and feel" of
the site. The deliverable from creative is HTML pages that the customer has
approved. This is a seperate thread from Application Development. Developers
like myself focus on putting the data in the pages. We can take the HTML
pages produced by creative, changed their extension to .jsp, add actions to
the <form> tags and drop in <jsp:useBean> tags and send it down the line.
We tried the XSL approach about 6-8 months ago and got burned. The problem
was that after creative produced the HTML that met the customer's approval,
developers had to deconstruct the HTML and reproduce it again using XSL.
Lots and lots of development hours were spent trying to reproduce with XSL
what was already there to begin with, a workable HTML document. The gains of
going the XSL route didn't outway the costs in development hours.
Just my .02.
ryan
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
