cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Baptiste Quenot (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-1651) Null locator in EffectPipe triggers NPE
Date Mon, 23 Jan 2006 14:40:10 GMT
     [ http://issues.apache.org/jira/browse/COCOON-1651?page=all ]
     
Jean-Baptiste Quenot closed COCOON-1651:
----------------------------------------

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

Committed, thanks!

> Null locator in EffectPipe triggers NPE
> ---------------------------------------
>
>          Key: COCOON-1651
>          URL: http://issues.apache.org/jira/browse/COCOON-1651
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Forms
>     Versions: 2.1.8
>  Environment: Operating System: Linux
> Platform: PC
>     Reporter: Tom Green
>     Assignee: Cocoon Developers Team
>      Fix For: 2.2-dev (Current SVN), 2.1.9-dev (current SVN)
>  Attachments: EffectPipe.java.diff, cforms-npe-bug.tgz
>
> I am getting an NPE at line 488 in EffectPipe.java which is reliably triggered
> by simply putting an XSLT transform in the template pipeline at any point BEFORE
> the forms template transformer.  It didn't show up in the stack trace, but I
> traced it   to the call to EffectPipe.beginBuffer() in cases where locator is
> null.  For some reason, locator is null in case there is an xsl transform in the
> pipeline right before the forms transformer.  I'm including a zip of the
> relevant files to recreate the problem using the stock "registration" sample
> form, as well as a simple patch that works around the NPE.  I'm not sure if this
> is the *correct* way to fix this bug, since I don't really understand what it
> means for the locator to be null in this context, but it appears to work fine
> for me.  Note that in the included sitemap you just need to comment out the
> <transform src="xsl/identity.xsl"/> and the bug goes away.

-- 
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