Yes. There are at the moment, 2 XML streams representing data (one
representing a menu and the other content) and, at the moment, we are using
another to represent error information. All the XML is aggregated into a
single XML document using a basic XSP template. This template is
transformed by an XSL file that is configured as part of the action mapping.
This XSL file uses <xsl:include> to include individual stylesheets to handle
each area of the screen (corresponding to each XML data source). I
understand that using JSP and the struts taglibs there would be more
"standard" ways of doing this. However, we chose Struts purely to fulfill
the controller part of MVC and don't really feel we need any of struts' view
components. Our data source is XML based so using XSL seems like the most
appropriate solution. This way some people can concentrate on content
generation while others work on the look and feel.
> -----Original Message-----
> From: Mahesh Bhagia [SMTP:[EMAIL PROTECTED]]
> Sent: 11 July 2001 17:33
> To: [EMAIL PROTECTED]
> Subject: RE: XML/XSL/Struts Architecture
>
> Hi John,
>
> So you mean that there are 2 XML's respresenting data and other
> respresenting error.
> (correct me)
>
> Thanks
>
>
>
> -----Original Message-----
> From: O'Reilly John [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 10:57 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: XML/XSL/Struts Architecture
>
>
> Our initial idea is to store XML representing the error message in the
> request context. The XSP page (we actually have a single template XSP
> page
> which "aggregates" different streams of XML information e.g. menu,
> content,
> and error messages etc) reads this XML and it is then up to the XSL to
> display (if it exists) this error information as it sees fit.
>
>
> > -----Original Message-----
> > From: Mahesh Bhagia [SMTP:[EMAIL PROTECTED]]
> > Sent: 11 July 2001 15:11
> > To: [EMAIL PROTECTED]
> > Subject: RE: XML/XSL/Struts Architecture
> >
> > Thanks John,
> >
> > How you do go about doing error checking with XML. so you use "pattern
> > method mechanism" as per article form javaworld
> > "Strut your stuff with JSP tags" or some other mechanism
> >
> > All suggestions are welcome
> >
> > Thanks
> > Mahesh
> >
> >
> > -----Original Message-----
> > From: O'Reilly John [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, July 11, 2001 4:42 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: XML/XSL/Struts Architecture
> >
> >
> > Hi Mahesh,
> > We have started using Struts for an application that uses XSP/XML/XSL
> > (using
> > Cocoon). Instead of specifying a JSP page in the struts
> configuration
> > file
> > we specify a XSP page. This server page is responsible for getting
> XML
> > data
> > from some data object set up in the action classes (we are using
> > attributes
> > in the session object for now). We also have extended ActionMapping
> to
> > allow us to specify the XSL stylesheet in the struts configuration
> file.
> > You are right about the use of tag libraries - that is one aspect of
> > struts
> > that you potentially lose out on using the above approach.
> > Regards,
> > John
> >
> >
> > > -----Original Message-----
> > > From: Mahesh Bhagia [SMTP:[EMAIL PROTECTED]]
> > > Sent: 10 July 2001 17:24
> > > To: Apache Struts (E-mail)
> > > Subject: XML/XSL/Struts Architecture
> > >
> > > Hi,
> > >
> > > In our application, we are using XML/XSL to generate JSP and plan to
> > use
> > > Struts for submitting data from HTML forms. Has anyone used / know
> > > if this architecture works. my thinking is ( correct me if wrong ) ,
> > we
> > > will not be able to use tag libraries coz of XML/XSL combination for
> > > generating pages. unique thing about this application is structure
> of
> > > HTML is different for each client.
> > >
> > > Thanks
> > > Mahesh
> > >
> > >
