Thanks for the reply, Antonio. But hey, doesn't this mean I'd have to manually code those url's one way or another? Cause if it means that, I think it would be clearer if I stick with the original pipeline (the one with the aggregation). Would that be so wrong (like a "never do this" for a best practice)?
-----Original Message----- From: Antonio Fiol Bonnín [mailto:[EMAIL PROTECTED] Sent: 19 decembrie 2005 13:44 To: [email protected] Subject: Re: Easier indexing You can try with xinclude or cinclude on a dynamically generated source plus some transformations. -- Antonio 2005/12/19, Dan Nicolici <[EMAIL PROTECTED]>: > > > > Hi! > > > > I am indexing my website with the LuceneIndexTransformer like this: > > > > <map:match pattern="site/indexAll"> > > <map:aggregate element="page"> > > <map:part > src="cocoon:/content/menu?cocoon-view=content"/> > > <map:part > src="cocoon:/content/newspapers?cocoon-view=content"/> > > <map:part > src="cocoon:/content/books?cocoon-view=content"/> > > > </map:aggregate> > > <map:transform src="xsl/xml2lucene.xsl"/> > > <map:transform type="index"/> > > <map:serialize type="xml"/> > > </map:match> > > > > The content pipeline is: > > > > <map:match pattern="content/*"> > > <map:generate > src="{global:template}xsp/{1}.xsp" type="serverpages"> > > <map:parameter name="location" > value="{request:contextPath}/web/site/{1}"/> > > </map:generate> > > <map:transform > src="{global:template}xsl/{1}.xsl"/> > > <map:serialize/> > > </map:match> > > > > Can (or how can) I achieve the following: > > > > <map:match pattern="site/indexAll"> > > <map:part src="cocoon:/content/*"/> > > <map:transform src="xsl/xml2lucene.xsl"/> > > <map:transform type="index"/> > > <map:serialize type="xml"/> > > </map:match> > > > > to eliminate the writing of all possible src's that can call the content > pipeline. > > > > Right now I think it is impossible, but am I wrong? -- Antonio --------------------------------------------------------------------- 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]
