Same environment. Haven't yet tried again, but will post results. > -----Original Message----- > From: Schultz, Gary - COMM [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 23, 2006 1:58 PM > To: 'users@cocoon.apache.org' > Subject: RE: cinclude usage/alternatives > > > What version of OS, Java SDK and Cocoon are you using? Under > Windows, SDK 1.5 and Cocoon 2.1.8 I also received the > cinclude element itself instead of the cinclude > transformation working, when the cinclude was placed after an > xslt transformation. When I went back to SDK 1.4.2_x > (1.4.2_10 in my case) the cinclude transformation worked > after the xslt transformation. > > -----Original Message----- > From: Bruyn Bill [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 23, 2006 9:17 AM > To: users@cocoon.apache.org > Subject: RE: cinclude usage/alternatives > > Thanks, Lars (and Derek and Sylvain). > > In the end I got it done with map:aggregate and a downstream > xslt (it was easy too - I just had to change my thinking a > little bit.) I tried the cinclude approach below, but I > actually couldn't get that to work. With this matcher: > > <map:match pattern="wrap-forms-template/*.jx"> > <map:generate > src="http://dev.drugfreeaz.org/treatment/wrapper.xhtml"/> > <map:transform src="context://stylesheets/pipeline-wrapper.xsl"> > <map:parameter name="pipeline" > value="cocoon:/forms/view/{1}.jx"/> > </map:transform> > <map:transform type="cinclude"/> > <map:serialize type="html"/> > </map:match> > > I end up with the cinclude element itself instead of the pipeline > results: > > <td><incl:cinclude src="the-pipeline"/></td> > > As if the cinclude transform never took place. What did I miss there? > > > -----Original Message----- > > From: Lars Huttar [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, February 21, 2006 9:35 AM > > To: users@cocoon.apache.org > > Subject: Re: cinclude usage/alternatives > > > > > > Bruyn Bill wrote: > > > For various reasons, I need to retrieve some markup from a remote > > > resource, and insert my jx result inline. e.g., I have > some remote > > > file called wrapper.xhtml that looks like > > > > > > <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC > > > "-//W3C//DTD XHTML 1.0 Transitional//EN" > > > > > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> > > > <html xmlns="http://www.w3.org/1999/xhtml";> > > > <head> > > > <title></title> > > > </head> > > > <body> > > > <table> > > > <tr> > > > <td>Here is some static content</td> > > > <td class="webapp">and a placeholder for dynamic > > stuff</td> > > > </tr> > > > </table> > > > </body> > > > </html> > > > > > > Where I need to replace the contents of //[EMAIL PROTECTED]'webapp'] with > > > 'whatever'. It isn't the way I would have chosen to put it > > together, > > > but it seems like a reasonable requirement that I should > be able to > > > handle with the sitemap and a cinclude transform. Right? > > > > > > No luck though with several hours of experimentation and the usual > > > looking through google, samples, wiki, archives, userdoc, > > etc. BTW, > > > the cinclude is really very slow... Is this the > > recommended method, > > > or am I barking up the wrong tree here? > > > > > As an alternative to using <map:aggregate>, you could run your > > wrapper.xhtml through a stylesheet transformation that replaces > > //[EMAIL PROTECTED]'webapp'] with <cinclude:include > > src="cocoon:/my-pipeline-for-whatever" />; then follow that > with the > > cinclude transform: > > > > <map:match pattern="something"> > > <map:generate src=".../wrapper.xhtml" /> > > <map:transform src="replace-td-with-cinclude.xsl" /> > > <map:transform type="cinclude" /> > > <map:serialize type="xml" /> > > </map:match> > > > > Does that address what you're trying to do? > > Lars > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
