> I'd say that HTML generation is useful when 1) the person writing the
> servlet code is the same as the person writing HTML;
Today I had the idea of using the OpenXML HTML parser to read in an HTML
file and generate ECS code from the HTML parser. Almost like a .jsp ->
servlet conversion type system. I think that would solve your #1 issue. ;-)
> 2) the code
> generating the HTML may not be part of the servlet directly, but called
> from it -- could happen when a component not only sends HTML to web
> browsers, but sends it as mail or displays it in a Swing component; 3)
> you want to support many presentations of the same base document -- for
> example, to be able to generate content for HTML 3.2 browsers that's
> different from content for HTML 4.0 browsers that use stylesheets; or 4)
> personal preference.. :) Sometimes it comes down to that.
>
> I haven't run into many of type 3) (does ECS do this? 'twould be handy
> Jon (nudge nudge, wink, wink)) but a good library should be able to do
> this sort of thing effortlessly.
#3 is an issue that is solved by using servlet frameworks that allow you to
write ECS code like that. ECS really isn't responsible for generating
content for different browsers any more than you are. ;-) Unfortunately,
this is still a process that must be done by hand and a framework is
responsible for serving the data depending on the browser.
-jon
___________________________________________________________________________
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
