You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Mi...@nag.national.com.au on 2001/02/28 05:51:06 UTC

struts and XSL



     There are many competing technologies to embrace the
     Model 2 pattern.

     I get the feeling that XML/XSL and Struts are mutually
     exclusive.  Is this a valid concern ??

Michael_J_Quinn@nag.national.com.au


__________________________________________________________________________
The information contained in this email communication may be confidential. You
should only read, disclose, re-transmit, copy, distribute, act in reliance on or
commercialise the information if you are authorised to do so. If you are not the
intended recipient of this email communication, please notify us immediately by
email to NABpost@nag.national.com.au or reply by email direct to the sender
and then destroy any electronic or paper copy of this message.  Any views
expressed in this email communication are those of the individual sender, except
where the sender specifically states them to be the views of a member of the
National Australia Bank Group of companies.  The National Australia Bank Group
of companies does not represent, warrant or guarantee that the integrity of this
communication has been maintained nor that the communication is free of errors,
virus or interference.



Re: struts and XSL

Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
Michael_J_Quinn@nag.national.com.au wrote:

>      There are many competing technologies to embrace the
>      Model 2 pattern.
>
>      I get the feeling that XML/XSL and Struts are mutually
>      exclusive.  Is this a valid concern ??
>

I'm not sure that they are mutually exclusive, but there is a choice you ned to make
for the "outermost" controlling architecture for your web application.

If your application is primarily content publishing, with data based primarly in
XML, you owe it to yourself to consider a framework like Cocoon, which is aimed at
precisely this type of environment.  That doesn't prohibit you from using the Struts
custom tag library (if your presentation is in JSP pages), but you probably will not
need the Struts controller environment.

If your application is primarily a dynamic business app, you owe it to yourself to
consider the controller framework inside Struts.  This doesn't prohibit you from
using XML, XSLT, and XSP -- you can still use them to create portions of the content
of your pages -- but you probably will not need the Cocoon site map capabilities.

>
> Michael_J_Quinn@nag.national.com.au
>

Craig McClanahan