Yes but I really wanted: genXML --> Java (via XSP) --> XSLT --> Serialize
I'm thinking from a background in JSP where logic can be written in Java either directly or via custom tags. I'm starting to think the only choice in the C2 framework is just XSLT. Dean McGowan wrote: > > Can you use 2 transforms instead ie: genXML --> XSLT --> XSLT --> > Serialize ? or does the XSP draw from another data - source .. just kind > of soundslike you want to re arrange your data then transform ?? could > be wrong too :) > > -----Original Message----- > From: Zack Angelo [mailto:[EMAIL PROTECTED]] > Sent: Sunday, 5 May 2002 8:45 AM > To: [EMAIL PROTECTED] > Subject: Re: XSP + Dynamic XML generator ?? > > Chris, > > Generally speaking, you don't use XSP to transform XML that has already > been > generated, you use it generate XML in the first place. So it seems that > you'd want to follow the typical pipeline layout, generate your XML with > XSP > based on parameters gathered from your datasource (perhaps via esql or > some > embedded java code). Then apply a stylesheet to that and serialize it. > So, > XSP->XSLT->Serialize. > > I'm sorry if I'm completely off, I don't quite get what you're trying to > do. > > -Zack > > On 5/3/02 2:03 PM, "Chris Wolf" <[EMAIL PROTECTED]> wrote: > > > > > I am working on a project where we have a datasource > > which produces XML based on certain parameters. I would > > like to use this as input to an XSP page which defines > > overall content structure (semantics) then, finally, > > apply a stylsheet appropriate for the invoking client. > > > > > > Problem: It seems that a pipeline must start > > with one, and only one Generator. The problem is > > that if I create an implementation of Generator > > which produces the XML, then I cannot use XSP > > (since the XSP code handler is itself a Generator). > > > > I then tried to implement the XML generator from an > > XSP page by invoking a method using xsp:expr, but then > > the whole document is treated as a single string. > > > > What I would like to do is some thig like: > > > > Ideas anyone? > > > > +---------------+ > > | XML Generator | > > +------+--------+ > > | > > v > > +---------------+ > > | XSP structure | > > +------+--------+ > > | > > +------v-----------+ > > | XSL presentation | > > +------+-----------+ > > | > > +------v--------+ > > | Serializer | > > +---------------+ > > > > --------------------------------------------------------------------- > > Please check that your question has not already been answered in the > > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
