Gilad, this is somewhat complicated, but very useful. The secret here
is to use the Tomcat remote debugging options.
Stop tomcat, then
$ cd $LPS_HOME
$ export DEBUG_TOMCAT=true
$ ant tomcat.start
This runs tomcat with these options:
-Xdebug -Xint -Xnoagent -Djava.compiler=NONE -
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=9999
I've only done the next step in IntelliJ IDEA, but you can probably
do it in Eclipse too -- find UI that talks about "connect to tomcat
servlet" and enter options based on the options specified above.
You should build the server with lots of debugging information
compiled in, and help Eclipse find the source. That is a difficult
task, and I haven't done it in a year.
Hope this helps.
-ben
On Dec 27, 2007, at 4:23 PM, Gilad Parann-Nissany wrote:
Hi
Sorry if this is a newbie question. I am new to the topic.
I'm in an existing OL app, which has the setup of Java classes on
the tomcat being called by xml-RPC from the (flash 9) OL client.
The Java classes are on the same Tomcat instance as the LPS servlet.
What I'm trying to achieve: set a breakpoint and line-by-line
debugging (in Eclipse if possible) of the Java classes (that are
running in Tomcat) when a call comes in from the client. Note I am
not trying to debug the lzx code but rather the server-side java code.
I've tried the Eclipse WTP and tried setting up Tomcat to debug
through that, which usually works; but starting that up together
with the LPS servlets did not work for me.
I am guessing there is some easy way - I just missed it. Any input?
Thanks
Gilad
Gilad Parann-Nissany
