Hi Nils, I don't think it's possible to say if cocoon is the right choice or not, but i'll try to give some possible answers to your questions.
----- Messaggio originale ----- Da: "Nils Kaiser" <[EMAIL PROTECTED]> A: [email protected] Inviato: 13/03/06 18.48 Oggetto: Is Cocoon the right choice? 1) Logical decisions in the pipeline depending on pipeline content... Unfortunately matchers and selectors are applied before content is actually generated. Actions could be an answer but they're not loved in the cocoon world. Anyway there is a way of doing it, althought it's not tidy, see next answer. 2) As we are working with a lot of information coming from different pages and 'following' links to get this information, we need a more dynamical approach to get content. I have only little knowledge of flow. Is it the answer?? Yes, in flow you can use processPipelineTo which invokes the sitemaps as many times you want, dinamycally composing (in flow) both the uri and the bizdata you pass to it. The result of the pipeline is written to an output stream and could then be sent again as a bizdata to the next sitemap invocation. I am very open to innovative solutions like having an own pipeline implementation or a DOM based framework which can adress content based decisions better. I am just afraid we might end with a kind of monster doing some ugly things to force cocoon to do thing it is not supposed to ;) No, you can solve this (IMMO) driving the sitemap invocations from the flow (thus having all the control you need) and implementing some custom components (a selector evaluating xpath on an xml bizdata for example) to further tune this control. Hope this is useful, Simone -- Simone Gianni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
