forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-675) upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site: etc.
Date Wed, 28 Sep 2005 06:14:47 GMT
    [ http://issues.apache.org/jira/browse/FOR-675?page=comments#action_12330669 ] 

Antonio Gallardo commented on FOR-675:
--------------------------------------

On Cocoon 2.1.8-dev (and I believe on cocoon 2.2.-dev it works too) I was able to run a sample
including namespaces. See this matcher with 2 LinkRewriterTransformer calls:

<map:match pattern="*.html">
       <map:generate src="docs/{1}.html"/>
       <map:transform type="linkrewriter" src="cocoon:/linkmap"/>

       <!-- +++++ For the pages that have a non empty default namespace  ++++++++++++ 
-->
       <map:transform type="linkrewriter" src="cocoon:/linkmap">
         <map:parameter name="namespace-uri" value="http://www.w3.org/1999/xhtml"/>
       </map:transform>

       <map:serialize/>
       <map:serialize type="xml"/>
     </map:match>

I am just wondering why this problem is raised by jxpath 1.2. I don't saw in the LinkRewriterTransformer
jxpath references at all. Can somebody try this on forrest? Here is too late right now and
I am sleeping. ;-)

> upgrading to commons-jxpath-1.2.jar causes failures with linkrewriter protocols site:
etc.
> ------------------------------------------------------------------------------------------
>
>          Key: FOR-675
>          URL: http://issues.apache.org/jira/browse/FOR-675
>      Project: Forrest
>         Type: Bug
>   Components: Core operations
>     Versions: 0.7, 0.8-dev
>     Reporter: David Crossley
>     Priority: Blocker
>      Fix For: 0.8-dev

>
> upgrading from commons-jxpath-20030909.jar to commons-jxpath-1.2.jar causes failures
with linkrewriter protocols site: etc. This happens in both modes: 'forret run' and 'forrest'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message