Re: Cocoon 2.2 flowscipt debugger possible?

[Robin Wyles]

Hi,




Robin






On 1 Aug 2008, at 15:29, Grzegorz Kossakowski wrote:

I just noticed this change this morning when I updated to latest trunk... lo and behold the flowscript debugger started up when I ran my app which seemed to cause all sorts of issues when testing in Eclipse, and using mvn jetty:run... So my question.... should the FlowScript debugger really be enabled by default for dev mode?

Hugh Sparks pisze:

I read a few posts that suggest that this is impossible, but I decided

to try the flowscript debugger anyway. I'm running under Tomcat, so

to this directory in my Tomcat installation:
   webapps\cocoon\WEB-INF\classes\META-INF\cocoon\avalon
I edited the file to enable the debugger and started Tomcat.
When I ran my cocoon flowscript application, the debugger
window appeared, but the application crashes. Here are some
highlights from the traceback:
       description The server encountered an internal error ()
       that prevented it from fulfilling this request.
       org.apache.avalon.framework.service.ServiceException:
       Exception during lookup of component with
       'org.apache.cocoon.components.flow.Interpreter/javascript'.
       (Key='AvalonServiceManager')
       org.springframework.beans.factory.BeanCreationException:
       Error creating bean with name
       'org.apache.cocoon.components.flow.Interpreter/javascript':
       Initialization of bean failed; nested exception is
       org.springframework.beans.factory.BeanCreationException:
       Unable to initialize Avalon component with role
       org.apache.cocoon.components.flow.Interpreter/javascript;
       nested exception is java.lang.IllegalStateException

I realized that Avalon is on the way out, but should this work?

Thanks to all,

I copied the file cocoon-flowscipt.xconf from the cocoon 2.2 svn truck If I remove the cocoon-flowscript.xconf file, the application works normally. What is the current best practice to use the debugger in its present form?

Hi Hugh,

This has been fixed in trunk, see:
http://article.gmane.org/gmane.text.xml.cocoon.cvs/27138



Also, you might be interested in following commit:
http://article.gmane.org/gmane.text.xml.cocoon.cvs/27140

--
Best regards,
Grzegorz Kossakowski

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

If you want to use this fixed version, you will need to checkout trunk and build it. Then just add SNAPSHOT dependency to your pom (of your project). There is no need to switch with all Cocoon dependencies to SNAPSHOT versions.

smime.p7s
Description: S/MIME cryptographic signature