cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Crossley (JIRA)" <>
Subject [jira] Commented: (COCOON-1616) source that declares namespace fails JXPath/Linkrewriter/Input Modules
Date Tue, 01 Nov 2005 03:10:03 GMT
    [ ] 

David Crossley commented on COCOON-1616:

Copying this comment over from the old closed Cocoon Bugzilla ...

------- Additional Comment #2 From 2005-10-31 08:41 [reply] -------

I'm not sure what the bug is in Forest, but I doubt it depends on #32360. JXPath
was working correctly (at least until it was broken while someone mistakenly
"fixed" 32360). There might be some problem in how Forest's XPath expressions
are designed to handle the default namespace, or it might be something
completely different.

> source that declares namespace fails JXPath/Linkrewriter/Input Modules
> ----------------------------------------------------------------------
>          Key: COCOON-1616
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: - Components: Sitemap
>     Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: other
> Platform: Other
>     Reporter: David Crossley

> At Apache Forrest we use the wonderful Cocoon Linkrewriter block. When we
> upgrade from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar then we get
> failures with the linkrewriter protocols "site:" etc.
> This issue can also be demonstrated as broken in the current Cocoon trunk
> samples for Linkrewriter. Make the following change to
> src/blocks/linkrewriter/trunk/samples/sitedemo/linkmap.xml and then note that
> the sample shows the links in their unresolved form.
> ------
> -<site href="">
> +<site href="" xmlns="">
> ------
> Not sure whether it is due to an incomplete implementation in the Linkrewriter
> or something to do with the Cocoon input modules or both.
> There is more discussion about the issue at Forrest
> There is a relevant note about the namespaces at

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message