Leszek Gawron wrote:
Sylvain Wallez wrote:
As a side note, the refactored NamespacesTable I committed yesterday
is a killer tool to cleanly handle namespaces (see
RedundantNamespacesFilter). I plan to use it in some transformers
that "consume" namespaces such as i18n, xinclude, etc to ensure the
consumed namespaces never passes through the transformer. That will
make cleaner and smaller web pages!
So this means the output page won't have the nasty:
<html xmlns:fi="http://apache.org/cocoon/forms/1.0#instance";
xmlns:jx="http://apache.org/cocoon/templates/jx/1.0";
xmlns:cinclude="http://apache.org/cocoon/include/1.0";
xmlns:dir="http://apache.org/cocoon/directory/2.0";>
Exactly!
titanium hero plate again ! :)
LOL! Thanks :-)
OT: What stage are cocoon stack traces in 2.1.x branch? I lack this
very much in trunk.
I'm working on it as we speak, adding a description to locations so that
we can associate e.g. an element name or flowscript function name to a
location.
I will also modify AbtractProcessingPipeline so that it dumps the full
chain of locations of the pipeline when an error occurs.
That will lead to stacktraces like:
<jx:forEach> -
resource://org/apache/cocoon/forms/generation/jx-macros.xml:103:10
<ft:repeater> - context://foo/bar.xml:23:12
<map:serialize> - context://foo/sitemap.xmap:45:6
<map:transform> - context://foo/sitemap.xmap:44:6
<map:generate> - context://foo/sitemap.xmap:43:6
showForm() - resource://org/apache/cocoon/forms/flow/js/form.js:30:-1
do_stuff() - context://foo/flow.js:10:-1
<map:call> - context://foo/sitemap.xmap:20:6
<map:mount> - context://sitemap.xmap:20:10
Looks cool, eh?
I plan to finish this in 2.1.x tomorrow and then port to trunk.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
