Joern Nettingsmeier wrote:
Andreas Hartmann wrote:
Joern Nettingsmeier schrieb:
hi *!
unless i'm very much mistaken, aggregate-fallback does not handle
namespaces correctly. i saw a case where the new common document element
did not retain its namespace.
Would you mind filing a bug and describe how to reproduce the problem?
i will. if you have the time, would you mind checking out the branch i
created yesterday? there is a problem now with
webapp/lenya/xslt/modules/modules2xinclude.xsl - it does not work, and i
thought it might be due to the fact that the document element now has a
namespace.
here's what comes out of the aggregate-fallback:// source when
publication.xconf is moved to a namespace:
<publication>
<name xmlns="http://apache.org/cocoon/lenya/publication/1.1";>Default
Publication</name>
....
</publication>
as you can see, the document element does not retain its namespace, and
the inner elements all get individual namespace nodes.
to reproduce:
svn co https://svn.apache.org/repos/asf/lenya/branches/trunk-rework-pubconf
build, run, go to default pub, import content. you will notice that in
the file menu, the "New <resource-type> Document" items are missing.
check out http://localhost:8888/modules/profiling/profile.html
(profiling is already enabled for the pipeline in question).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
