Hi All,
Hope all is well.
I've just checked-in support for using the Rhino JavaScript debugger
with Cocoon flow.
The Rhino debugger is a visual debugger that allows you to set break
points, step in and out of functions, watch global and local variables,
and generally is really useful for debugging and watching what is
happening inside of your flowscript.
By default, the debugger is disabled, to enable it, add/comment-in
the <debugger/> element in your flow.xconf/cocoon.xconf file, eg:
<component-instance name="JavaScript"
class="org.apache.cocoon.components.flow.javascript.JavaScriptInterpreter">
<load-on-startup>resource://org/apache/cocoon/components/flow/javascript/system.js</load-on-startup>
<reload-scripts>true</reload-scripts>
<check-time>4000</check-time>
<debugger>enabled</debugger> <!-- this line enables the flow debugger -->
</component-instance>
When the <debugger/> element is present, all threads that create
a javascript interpreter will operate via a Rhino visual debugger
instance.
An example screenshot of what this looks like is available at
http://cvs.apache.org/~crafterm/debugger.jpg
Well, so far testing in my environment with the flow examples has
proved successful, so hopefully others also find it of use, if there's
any problems/comments/sugguestions, please feel free to let me know.
Last but not least, a big thank you to Yaar Schnitman and
Christopher Oliver for their help with the Rhino debugging API's.
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: ManageSoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&'
&&&&.
&&&&&&&:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
