Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <25227087.1171843385659.JavaMail.jira@brutus>
Date: Sun, 18 Feb 2007 16:03:05 -0800 (PST)
From: "Grzegorz Kossakowski (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2008) servletContext of BlockPathModule
 persists between seperate requests
In-Reply-To: <25330575.1171023066316.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COCOON-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474047 ] 

Grzegorz Kossakowski commented on COCOON-2008:
----------------------------------------------

I've tested your changes with refactored Forms (they use block-path module quite heavily) and everything works fine.

Thanks. Close this issue, please.

> servletContext of BlockPathModule persists between seperate requests
> --------------------------------------------------------------------
>
>                 Key: COCOON-2008
>                 URL: https://issues.apache.org/jira/browse/COCOON-2008
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Blocks Framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: COCOON-2008-prototype-scope.txt, COCOON-2008.txt
>
>
> The same servlet context is being reused between _separate_ requests leading to returning invalid absolute uri's.
> It seems that this line:
> this.servletContext = CallStackHelper.getBaseServletContext();
> is being called only once, when BlockPathModule is used first time, and then servletContext is never null (holds old value).
> I'm not sure, but it seems that life cycle of this class is not set up correctly. Even though I'm going to figure it out, it would be great if someone with better Spring/Cocoon internals knowledge could take a look on this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.