[
https://issues.apache.org/jira/browse/COCOON-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski (aka g[R]eK) updated COCOON-2008:
------------------------------------------------------
Attachment: COCOON-2008.txt
I attach the patch that shows bugged behavior. Apply it to
cocoon-servlet-service-sample and hit:
1. http://localhost:8888/blocks-test/cocoon-servlet-service-sample1/sub/abs
you'll get /cocoon-servlet-service-sample1/test as @abs attribute (correct)
2. Then access
http://localhost:8888/blocks-test/cocoon-servlet-service-sample2/sub/abs
and should get the same value as in previous point which is not correct.
> 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 (aka g[R]eK)
> Fix For: 2.2-dev (Current SVN)
>
> Attachments: 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.
