25 Aug 12:05
[jira] Created: (COCOON-2241) The commandline is not working since cocoon-1985
From: Thorsten Scherler (JIRA <jira <at> apache.org>
Subject: [jira] Created: (COCOON-2241) The commandline is not working since cocoon-1985
Newsgroups: gmane.text.xml.cocoon.devel
Date: 2008-08-25 10:07:44 GMT
Subject: [jira] Created: (COCOON-2241) The commandline is not working since cocoon-1985
Newsgroups: gmane.text.xml.cocoon.devel
Date: 2008-08-25 10:07:44 GMT
The commandline is not working since cocoon-1985
------------------------------------------------
Key: COCOON-2241
URL: https://issues.apache.org/jira/browse/COCOON-2241
Project: Cocoon
Issue Type: Bug
Components: * Cocoon Core
Affects Versions: 2.1.12-dev (Current SVN)
Reporter: Thorsten Scherler
Fix For: 2.1.12-dev (Current SVN)
Updating forrest to use cocoon-2.1.x, I found a problem in the
AbstractCachingProcessingPipeline.
I am not sure whether someone is using the cocoon cli ATM. Forrest is
based around this component.
https://issues.apache.org/jira/browse/FOR-955?focusedCommentId=12624340#action_12624340
I found that in
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline line 245
Object lock =
env.getObjectModel().get(HttpEnvironment.HTTP_REQUEST_OBJECT);
the lock is null which causes the NPE in the end.
The problem is that the cli environment does not store the requested object.
--
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RSS Feed