cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <>
Subject [jira] Closed: (COCOON-1742) EncodeURLTransformer can get a StackOverflow in jakarta regexp
Date Fri, 05 May 2006 14:01:28 GMT
     [ ]
Ralph Goers closed COCOON-1742:

    Fix Version: 2.2-dev (Current SVN)
                 2.1.10-dev (current SVN)
     Resolution: Fixed

EncodeURLTransformer has been modified to use JDK 1.4 regular expressions.  The modification
was released in 2.1.9 but that fix was in error (the error can be circumvented by manually
configuring the transformer with expressions that end with wildcards to match the end of the
string).  The final fix is in 2.1.10 and in trunk.  The fix is only available in 2.1.10 when
compiling with JDK 1.4. JDK 1.3 will still use the old version of the EncodeURLTransformer.

> EncodeURLTransformer can get a StackOverflow in jakarta regexp
> --------------------------------------------------------------
>          Key: COCOON-1742
>          URL:
>      Project: Cocoon
>         Type: Bug

>   Components: * Cocoon Core
>     Versions: 2.1.8, 2.2-dev (Current SVN)
>     Reporter: Ralph Goers
>     Assignee: Ralph Goers
>      Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)

> EncodeURLTransformer uses jakarta regexp and calls RE.match(). This method ends up calling
matchNode() which recursively calls itself. This is slow and has the potential of causing
a StackOverFlowException .Numerous issues have been opened on jakarta regexp regarding this
but there are no plans to address this.  I have run tests that show that regexp is much slower
than the JDK regular expressions and also slower than ORO.
> The fix for this will be to modify the EncodeURLTransformer in 2.2-dev to use the JDK
regular expressions.  Since the JDK regular expressions are only available in JDK 1.4 they
cannot directly be used in the 2.1 branch.  Most likely Oro will be used instead.

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