Hello,
About http://issues.apache.org/jira/browse/COCOON-1715
What is the best way to deal with this? Add servlet.jar in
the Loader's classpath when running the CLI? Or remove the
continuations-manager from cocoon.xconf by creating a new optional
flow block?
Your feedback will
Jean-Baptiste Quenot wrote:
Hello,
About http://issues.apache.org/jira/browse/COCOON-1715
What is the best way to deal with this? Add servlet.jar in
the Loader's classpath when running the CLI? Or remove the
continuations-manager from cocoon.xconf by creating a new
:
* loader.verbose
* loader.class.path
[PATCH] Allow ContinuationsManagerImpl to run in CLI
Key: COCOON-1715
URL: http://issues.apache.org/jira/browse/COCOON-1715
Project: Cocoon
Type: Bug
Components: * Cocoon
not executed. What is the best way to
deal with this? Add servlet.jar in the Loader's classpath when running the
CLI? Or remove the continuations-manager from cocoon.xconf by creating a new
optional flow block?
[PATCH] Allow ContinuationsManagerImpl to run in CLI
[ http://issues.apache.org/jira/browse/COCOON-1715?page=all ]
Jean-Baptiste Quenot reassigned COCOON-1715:
Assign To: Jean-Baptiste Quenot
[PATCH] Allow ContinuationsManagerImpl to run in CLI
[PATCH] Allow ContinuationsManagerImpl to run in CLI
Key: COCOON-1715
URL: http://issues.apache.org/jira/browse/COCOON-1715
Project: Cocoon
Type: Bug
Components: * Cocoon Core
Versions: 2.1.9-dev (current
