Armin Ehrenfels wrote: > Vadim, > > first of all, thank you for your reply.
<snip/> >> There are multiple ways: >> >> 1. Have two pipelines, one with XSP and second with RequestGenerator, >> then map:aggregate them together, XSLT as necessary, and serve it >> HTMLed. >> >> 2. Have XSP including other pipeline with RequestGenerator with the help >> of util logicsheet (documented, and also frequently asked/answered on >> this list), then resulting XSP you could XSLT transform, and serve as >> HTML or whatever you want. >> >> 3. Mix in some XSLT/SQL/LDAP transformations to 1 or 2, or combine them >> all together. >> >> >> > All interesting solutions, but none of them will make the XML request > data available to further processing. > Why isn't It depends on what do you mean under "available to further processing". All solutions outlined above allow get input XML, transform as necessary, perform RDBMS/LDAP/XMLDB operations on it, and create output out of it. Of course, you can always get this XML from your action, using similar technique (inclusion). It was outlined several times on this list how to get content of the pipeline in the action. One can always use XSPAction as well, which simplifies this to the level of tags. Vadim --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
