Debugging Nucleus components in JBoss with Eclipse

May 27, 2007

It seems that ATG developers are creatures of old habits. Most of them use VI or Emacs because they are used to it. Perhaps because they think it is better…. Only my observation of course. For all I know a lot of them are using Textmate with their custom ATG bundles.

And debugging? : through debug logging statements…

Since Java 1.2 we have the Java Platform Debugger Architecture. It amazes me how few are using it..

If you don’t know how to debug with JPDA when developing for ATG on JBoss with Eclipse it’s easy:

  • First start JBoss with debugging enabled. Do this by adding the line:

JAVA_OPTS="$JAVA_OPTS -Xdebug -Xrunjdwp:transport=dt_socket, address=5000,server=y,suspend=n"

to the run.conf file in the <JBOSS_HOME>/bin folder and then

  • create a debug configuration in Eclipse. Use the Remote Java Application, Socket Attach. Use the port as defined in the JAVA_OPTS. Port 5000 in this example.

It should look something like this:
Eclipse debugging

Happy debugging

Little ATG annoyances

March 27, 2007

I’m a complete ATG newbie. So perhaps some stuff is due to my inexperience, but things which seem odd to me:

Eclipse ATG plugin

When doing the New ATG Module in Eclipse a manifest is created with


There is a double DAS entry there.


I missed the create J2EE application under the ACC. It seems this is only available if you use DAS. Since I’m using JBoss, this is not available. Why is this?

More items are missing in the ACC. Well the ACC is going the way of the mammoth I guess.


Positive: It seems that Dynamusic from Developing ATG Applications is going to work. The Solid SQL script creating the Dynamusic tables was accepted by MySQL (after removing the drop statements). At least the first chapter worked. Although you have to use Eclipse in stead of the ACC.