Hello Jeroen,

Thanks for your help. As I understand your suggestion, the idea is to generate a document with the (C)Include elements required, and then include the dynamically created list of documents with an include transformation. I assume I can replace the JX-template with something else that can dynamically create the Include document. This sounds excellent.

My remaining question regarding this solution is whether the included documents will be read as is from the db/file system, or whether I can specify the "cocoon:" protocol in the src attribute in the include statements, to have the requests processed by the sitemap (I need the sitemap processing of each include for my application logic)? I could use the external/extended version of the Include statements, specifying the server and all, but that requires me to either dynamically generate the correct server address, or change it manually whenever I move the application from the development computer to the deployment server. Not a big thing, but it would definitely be nicer to just use the cocoon: protocoll:-)

Thanks again!

Best regards,
Sjur

Den 12. jun. 2006 kl. 17.06 skrev Jeroen Reijn:

Hi Sjur,

I do not know of any solution in the sitemap, but you are able to do this:

It should be something like this in pseudo-code:

<map:generate src="request.xml" type="jx/>
<map:transform type="include"/>
<map:serialize type="xml"/>

Step1. JX template generator

The generator generates a JX-template. The JX-template has the cocoon.request object available to iterate through. You can create <include src="file"/> elements for the include transformer.

Step2. (C)Include transformer

The (C)Include transformer will fetch your documents from your DB.


For more information about both components please take a look at:

http://cocoon.apache.org/2.1/userdocs/flow/jxtemplate.html

and

http://cocoon.apache.org/2.1/userdocs/cinclude-transformer.html

I hope this will help you out.

Regards,

Reijn


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to