Yes... As XSP is a generator, should I write my own transformer or
aggregator... Give me an answer, please... ;(
The question again:
I want to produce a html from a xml (not XSP) page but depending on the
session object there moght be an additional element. In C1 it worked with
XML->XSP->XSLT->HTML. But how does it (best) work with C2?
XML->Aggreation->XSLT->HTML or XML->MyTransformer->XSLT->HTML?
-----Ursprungliche Nachricht-----
Von: giacomo [mailto:[EMAIL PROTECTED]]
Gesendet: Sonntag, 10. Juni 2001 15:26
An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: Adding dynamically element
On Sun, 10 Jun 2001, Samuel ARNOD-PRIN wrote:
> I can not answer correctly to your question...
>
> but logically there should be a way to do something like this :
No, there is no logic in there.
An XSP page is a generator, point. A C2 pipeline has only one generator.
Transformers cannot produce or be transformed into xsp pages. This is not
the
concept.
Giacomo
> <map:match pattern="**.xml">
> <map:generate src="{1}.xml"/>
> <map:transform src="myfile.xsp.xsl">
> <map:generate type="serverpages" src="myfile.xsp.xsl"/>
> </map:transform>
> <map:serialize/>
> </map:match>
>
> otherwise, look in the MAP dtd or schema ...
>
> ---------------------------------------------------------------------
> 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]>
