Comments on: Trouble with Alfresco? Console yourself

By: Florian

Florian — Wed, 28 Sep 2011 17:34:58 +0000

For anyone looking for an easier way to develop Javascript for Alfresco I can recommend my Javascript Console extension that can be found in Share-Extras: http://code.google.com/p/share-extras/wiki/JavascriptConsole

By: Trying out Activiti: Examples that leverage Alfresco’s new workflow engine | ecmarchitect.com

Thu, 28 Apr 2011 04:56:02 +0000

[...] advanced workflow. It has always been a puzzle to me as to why the workflow console (along with others) can only be navigated to directly using an unpublished URL. That head-scratcher still remains, but [...]

By: : : blyx.com : : Blog : : Toni de la Fuente : : » Blog Archive » Alfresco Hack: Las consolas “escondidas” de Alfresco

Mon, 21 Jun 2010 05:52:50 +0000

[...] Cuando he terminado de escribir el artículo he hecho una búsqueda en Google y me encuentro esto, un post del gran Jeff Potts sobre esto [...]

By: jpotts

jpotts — Sun, 30 May 2010 03:28:45 +0000

Depends on what you’re doing. For example, in Share, if you do nothing else, Share will use the minified JavaScript files. However, you can turn on debug in the Share custom config and that will force the expanded JavsScript files to be used, which are much easier to debug.

I haven’t seen the everything-on-one-line problem with repository tier JavaScript except for maybe Alfresco JavaScript in jBPM actions. In that case, not only is it hard to step through but a line comment (“//”) will end up commenting out all of the JavaScript that follows.

Jeff

By: Michiel Verkaik

Michiel Verkaik — Wed, 19 May 2010 15:53:05 +0000

For some reason, the JavaScript debugger shows all lines of code on one line. It makes it impossible to step into or step over.

By: jpotts

jpotts — Tue, 02 Feb 2010 20:07:06 +0000

Francois,

Enabling the Rhino JavaScript debugger will cause a Java swing app to launch when the server starts up. Obviously, this will only work when you are running the app server on a box with a GUI (or are otherwise redirecting the graphical output to a terminal somewhere).

Once the GUI launches, it will look very familiar to you if you’ve ever used a stepping debugger of any kind. You can use it to set breakpoints, dump variable values, and step through code.

I should add that at the time I wrote that blog post, I hadn’t used the Rhino debugger very much, but as web scripts moved from Java to JavaScript and as I started doing more with Surf and Share, it became a really useful tool.

Jeff

By: Francois

Francois — Tue, 02 Feb 2010 19:40:44 +0000

Hi,

You mention the JavaScript debugger and how to enable it, but can you please go futher. Where does the output from the debugger go? How do you look at it?

Thanks
Francois

By: jpotts

jpotts — Wed, 27 May 2009 21:33:00 +0000

The JavaScript debugger is very useful. Rather than enable it through a web script, I enable it through log4j.properties:

http://ecmarchitect.com/archives/2008/12/09/871

You can use it to debug any server-side JavaScript running in Alfresco. That includes:
– Web Scripts (both repository tier and Surf tier)
– JavaScript inside a jBPM workflow
– JavaScript executed through an “execute script” action
– JavaScript-based actions

Being able to step back-and-forth through sometimes significant amounts of JavaScript is definitely a productivity booster.

By: Kyle

Kyle — Wed, 27 May 2009 20:57:49 +0000

The javascript debugger can also be enabled through one of the webscripts. I’m still trying to figure out what it’s useful for. I’d like to be able to debug my webscripts with a live debugger.

By: Debugging jBPM workflows | eshea.net

Debugging jBPM workflows | eshea.net — Fri, 30 Jan 2009 21:32:30 +0000

[...] for a full list of “hidden” consoles check out Jeff’s great post Trouble with Alfresco? Console yourself). However, very quickly I realized that the Eclipse / deploy / workflow console cycle to create and [...]