jon wrote:
----------------------------------------------------------------------------
#2. What I would like to do from the webmacro/freemarker/cocoon perspective
is essentially replace the Servlet portions of those tools with a Screen
portion. That way, essentially all the Screen is doing is forwarding
requests onto the processing engines for the page parsing. If you think
about it, W/F/C are essentially servlets with a text parser on the back end.
If we can call that parser on the back end directly (by passing the servlet
portion) and pass it the information it needs, then that should be all we
need to do. Just replace the servlet portion of things. Now, where I expect
that we will run into problems is that I have doubts about WebMacro having
been designed to have this done. I believe that Cocoon and FreeMarker are
designed this way.
------------------------------------------------------------------------------
jon, Aren't WebMacro and FreeMarker proprietary solutions for generating html
content from templates? I think your right that jsp isn't a good solution.
Wouldn't developers be better advised to use the XSL/XML combination, as does
Cocoon, to generate html from templates?
I'm currently using Turbine with an XSL processor to generate html. I'm using
ECS to compose the html from 1 to many XSL transformations. I'm looking forward
to the Turbine samples using Cocoon.
For intranet applications, I think that most will want to return XML to the
browser and implement the transformations in the browser. Can anybody point me
to some information on doing this job with Mozilla?
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
