cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <ba...@webslingerZ.com>
Subject [c2] namespace bug in aggregator
Date Fri, 27 Apr 2001 04:51:57 GMT
okay, i tracked down the namespace problem i had encountered and tried to
blame on xalan. as it turns out, it's almost certainly the aggregator.
here's a snippet of sitemap:

   <map:match pattern="*">
    <map:aggregate element="root">
     <map:part src="plain/meta"/>
     <map:part src="plain/{1}"/>
    </map:aggregate>
    <!-- log point 1 -->
    <map:transform type="log"/>
    <map:transform type="xinclude"/>
    <map:act type="resource-exists">
     <parameter name="url" value="context://style/{1}.xsl"/>
     <map:transform src="style/{../1}.xsl"/>
    </map:act>
    <map:transform src="style/wziml-html.xsl"/>
    <map:serialize type="html"/>
   </map:match>

   <map:match pattern="plain/*">
    <map:generate src="content/{1}.xml" type="serverpages"/>
    <!-- log point 2 -->
    <map:transform type="log"/>
   </map:match>

when i request the 'clients' url and look at the log generated by log
point 2, before the aggregation has occured, i find that the clients
element (correctly) has no namespace:

INFO    41899   [cocoon  ] (HttpProcessor[8080][3]): [startElement]
uri=,local=clients,raw=clients

but if i look at the log generated by log point 1, immediately after
aggregation has occured, i find that the clients element has been assigned
a namespace:

INFO    66950   [cocoon  ] (HttpProcessor[8080][2]): [startElement]
uri=http://intranet.webslingerZ.com/xml/site/v1,local=clients,raw=clients

ta-da. anyone want to venture a patch?

- donald


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message