Hello,
I've been trying to integrate the TDK 2.1 into VisualAge to take advantage of
its nice debugging environment, using parts of the information provided by
http://www7.software.ibm.com/vad.nsf/Data/Document2390?OpenDocument&p=1
This method allows to run Tomcat under VA without importing the Tomcat .jar
files into the VA repository, and it works (I can provide more details if anyone
is interested).
In my case, the method suggested in http://fire.idbsoft.com/tdk-va-howto.html
doesn't work, because classes are not found at appl runtime when imported into
VA.
Ok, Tomcat works, but the trouble starts when trying to integrate Turbine
webapps, because it seems that they can't be run by Tomcat under VA as simple
servlets can.
The only way i've been able to run them has been as "external" classes, loaded
dynamically by VA, by setting the webapps/newapp/web-inf/classes and /lib
directories in the VA project_resources directory exactly as they are in the
ordinary TDK settings.
Fortunately there is a way in VA to debug external classes (see the above
reference), provided you have the corresponding source. But I've been unable to
use it with Turbine: the breakpoints set in the source code do not stop the
execution. The breakpoints set as "break on method enter" do stop the execution,
but then nothing more can be done because it says the source is not available
(although it is when the breakpoints are set).
Has anyone actually suceeded in debugging Turbine apps under VisualAge? Can
these problems be caused by Turbine using its own special mechanisms when
requesting class loading to the underlaying VM?
Thanks for any suggestion that can help.
Pere
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
