cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Fagerstrom (JIRA)" <>
Subject [jira] Commented: (COCOON-2008) servletContext of BlockPathModule persists between seperate requests
Date Tue, 13 Feb 2007 22:39:05 GMT


Daniel Fagerstrom commented on COCOON-2008:

I added some faulty code while testing call stack scoped beans. My intention was to use a
scope proxied servlet context from the setServletContext if such a property was present in
the configuration and otherwise get the current call stack frame. But instead I just got the
current call stack frame the first time the getAttribute and used that value to set the property.
So in the sequel the same value was used.

This problem could be fixed by using prototype scope as you suggested. But it seemed better
to continue to have singleton scope and fix the faulty logic. So I did that.

Please check that it works in your context.

> servletContext of BlockPathModule persists between seperate requests
> --------------------------------------------------------------------
>                 Key: COCOON-2008
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Blocks Framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski (aka g[R]eK)
>             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.

View raw message