Hi,
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
Robin Wyles pisze:
Hi,
Hi Robin,
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
Hi Grzegorz,
I get many errors like this:
Exception in thread AWT-EventQueue-0
java.lang.ArrayIndexOutOfBoundsException: No such child: 1
at java.awt.Container.getComponent(Container.java:280)
at org.mozilla.javascript.tools.debugger.FileWindow.updateToolTip
(SwingGui.java:2181)
Robin Wyles writes:
[...] So my question should the FlowScript debugger really be
enabled by default for dev mode?
Grzegorz Kossakowski replies:
Could you elaborate on these issues you face? If there are some serious
problems then I think we'll switch it off again.
Actually, you can do
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
I copied the file cocoon-flowscipt.xconf from the cocoon 2.2 svn truck
to this directory in my Tomcat installation:
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
I copied the file cocoon-flowscipt.xconf from the cocoon 2.2 svn truck
to this directory in my Tomcat installation:
