hi !

i have the following scenario:

two modules:

"xmldb", a module to query an exist xml database. in its sitemap it contains a resource "xmldb", which is a complex chain of transformers:

  <map:resource name="xmldb">
    <!-- expand any jx parameter references in the query -->
    <map:transform type="jx"/>
    <!-- transform xq:query element into cinclude xmldb query -->
    <map:transform type="xslt" src="xslt/xmldb-preprocessing.xsl"/>
    <!-- perform the query by sending a POST request
         to the xmldb query handler -->
    <map:transform type="cinclude">
      <map:parameter name="support-caching" value="false"/>
    </map:transform>
    <!-- clean up result from the xqueryhandler -->
    <map:transform type="xslt" src="xslt/xmldb-postprocessing.xsl"/>
  </map:resource>


"people", a module that generates staff pages by querying said database.
in the "people" sitemap, i want to re-use that resource to keep things modular:

<map:generate src="queryPerson.xml"/>
<map:call resource="cocoon://modules/xmldb/xmldb"/>
<map:transform type="xslt" src="xslt/person2html.xsl"/>
<map:serialize type="xml"/>

of course the map:call does not work, because resources have to be local.

how can i accomplish this? iiuc i cannot use an entire pipeline with map:mount, because the generation must happen in the "people" sitemap, (the people module contains the query file).

i could think of having a callback-style pipeline in "xmldb" that gets passed a src parameter of the form "cocoon://modules/people/queryPerson.xml", but i would like to avoid it because it seems unidiomatic and rather complicated.


thanks in advance for any ideas!

jörn



--
"Open source takes the bullshit out of software."
        - Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736

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

Reply via email to