Hi,
Following the discussion we have decided to use an approach using the filter
features of the new servlet specifications. A application foo will follow
this steps:
0. some filtering is done for session stuff, security, etc.
1. the request is going to a controller servlet which is doing whatever it
should do (using beans for making db connection and computing and so on ...)
2. the request is including JSP which are ouputing an XML containing only
the logic data with some custom tags(a.xml)
3. a first filter will get the text content (probably also with a JSP and a
db connection behind) and include it in the XML document (b.xml)
4. a second filter transform the XML in HTML with XSL
5. a last filter can handle inclusion of static html files (like other part
of the web site)
Our web designer will receive some sample XML output files (of type a.xml)
and write then the XSL stuff, and the XML document b which is containig the
different texts, image references, etc.
I think for us it's a proper enough approach you have the whole JAVA code in
the servlets, filters, and tags. The JSP files look very clean containing
only a few custom tags. We are acheiving this way agood separation of the
logic, the content and the style of a web application.
Of course it take time at the beginning, but later on it's really easy to
add a wap version of a web site or to change the look and fell without
involving a single JAVA developer or to correct the java part if the xml
output is well defined.
Guillaume
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
