> My intention is to render the XML+XSL to HTML within the
> Servlet, rather than leaving it to the browser to render.
> This avoids incompatibility with older browsers.
>
> What I am trying to achieve is a "pluggable" user interface
> to my Servlet. I.e. separating out the presentation from the
> logic. Eventually there may be several different user
> interfaces (i.e. several different sets of XSL files), all
> running of the same servlets (i.e. generating the 'same' XML
> data). I want to do this without compromising the flexibility
> of the logic side, but without making the user interface too
> complicated to redesign.
>
> My main concerns are:
> 1) Performance. I don't want the rendering to become a bottleneck.
> 2) Which XML/XSL engine to use (currently IBM's xml4j seems a
> good contender)
>
> Alternatively, I could forget about XML altogether. Can
> anyone suggest a better mechanism to separate out the
> presentation? Would I be better off persuing JSP's?
JSP currently does not offer real separation of content,
presentation and application logic. Right now JSP pages contain
Java Code mixed with HTML tags. You would have to wait for
JSP 1.1, which offers tag libraries or use something
proprietary like JRun's dynamic taglest to have better
separation.
But JSP and XML/XSL are not competitors. I use JSP together
with XML/XSL.
I think using XML/XSL is superior to other solutions because
with XSL you do not have to write code to create a view. And
because XSL is XML you can easily parameterize the view by
querying the DOM and changing a value.
Regards
Bernhard
___________________________________________________________________________
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
