You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Peter Lerche <pe...@easyspeedy.com> on 2004/03/24 15:00:05 UTC

Woody cannot find its FormManager

Hi,

I am trying to "upgrade" from jxForm to Woody on a 2.1.4 dest. installation.
For some reason the class org.apache.cocoon.woody.FormManager cannot be found 
when a pipeline calls this minimal flow js scripts 

function test(){
	var form = new Form("/woodyform.def");  // Yak! where is my FormManager
	form.showForm('/woodypage.wf');
}

I have tried to use 
cocoon.load("resource://org/apache/cocoon/woody/flow/javascript/v2/Form.js");
and 
cocoon.load("resource://org/apache/cocoon/woody/flow/javascript/woody2.js");
with the same result.

I have checked that cocoon-woody-block.jar contains the 
org.apache.cocoon.woody.FormManager and it does.


Cause:

org.apache.avalon.framework.component.ComponentException: Could not find 
component (key [org.apache.cocoon.woody.FormManager])

Full exception chain stacktrace:

Original Exception: org.apache.avalon.framework.component.ComponentException: 
Could not find component (key [org.apache.cocoon.woody.FormManager])
        at 
org.apache.avalon.excalibur.component.ExcaliburComponentManager.lookup(ExcaliburComponentManager.java:299)
        at 
org.apache.cocoon.components.CocoonComponentManager.lookup(CocoonComponentManager.java:324)
        at 
org.apache.cocoon.components.flow.javascript.fom.FOM_Cocoon.jsFunction_getComponent(FOM_Cocoon.java:363)
        at inv3.invoke()
        at 
org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:523)
        at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:438)
        at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
        at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:1105)
        at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190)
        at 
org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138)
        at 
org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121)
        at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244)
        at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.callFunction(FOM_JavaScriptInterpreter.java:719)
        at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:160)
        at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84)
        at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:165)
        at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:107)
        at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:162)
        at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:107)
        at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:136)
        at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:371)
        at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:312)
        at org.apache.cocoon.Cocoon.process(Cocoon.java:656)
        at 
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1112)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:354)
        at 
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
        at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1808)
        at 
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
        at org.mortbay.http.HttpContext.handle(HttpContext.java:1758)
        at org.mortbay.http.HttpServer.service(HttpServer.java:879)
        at org.jboss.jetty.Jetty.service(Jetty.java:456)
        at org.mortbay.http.HttpConnection.service(HttpConnection.java:790)
        at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:952)
        at org.mortbay.http.HttpConnection.handle(HttpConnection.java:807)
        at 
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:197)
        at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
        at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:501)


Thanks
-- 
Med venlig hilsen / Yours sincerely 
 
Peter Lerche
EasySpeedy ApS 
http://easyspeedy.com
_______________________________________ 
European Dedicated Server Hosting 
Extremely low prices, secure, and reliable

_______________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: Woody cannot find its FormManager

Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Mar 24, 2004, at 6:00 AM, Peter Lerche wrote:

> Hi,
>
> I am trying to "upgrade" from jxForm to Woody on a 2.1.4 dest.  
> installation.
> For some reason the class org.apache.cocoon.woody.FormManager cannot  
> be found
> when a pipeline calls this minimal flow js scripts
>
> function test(){
> 	var form = new Form("/woodyform.def");  // Yak! where is my  
> FormManager
> 	form.showForm('/woodypage.wf');
> }
>
> I have tried to use
> cocoon.load("resource://org/apache/cocoon/woody/flow/javascript/v2/ 
> Form.js");
> and
> cocoon.load("resource://org/apache/cocoon/woody/flow/javascript/ 
> woody2.js");
> with the same result.
>
> I have checked that cocoon-woody-block.jar contains the
> org.apache.cocoon.woody.FormManager and it does.
>

OK, does your cocoon.xconf contain a <woody-formmanager> element?  If  
not, have a look at the cocoon.xconf from a 2.1.4 build where the woody  
block was enabled.  Actually, if your cocoon.xconf is missing this,  
you'd better diff it against one from the build,  'cause you'll also be  
missing a slew of other Woody stuff, and who knows what else.

Also, just a tip... never mix flowscripts that load woody2.js in the  
sitemap w/ flowscripts that load v2/Form.js — bad things happen :-/.

HTH,
~ mark



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org