Hello all, 

 

I have been trying to connect the JPDA debugger (off command line and
through NetBeans) to the Ooo 2.0 in an attempt to start the debugging on
components and jobs. However, the JPDA debugger exists with a connection
refused exception. 

I try to bind the port 8000 on Ooo, which has the Java enabled to use my JRE
1.5, from the Tool/options/Java menu. I have also added the required JVM
flags -Xdebug and the -X flag specifying port 8000. I also tried the
blocking and non-blocking approaches in vain. 

 

>From what I understand from reading the dev guide and the posts on the
mailing list, I don't seem to have missed anything. However, the futile
attempt suggests the contrary. 

 

I d appreciate it if you can provide some hint on what may be going wrong.
Is there a way that I can start the Ooo 2.0 from command line with a java
<options> <Ooo main class> format?? 

 

I am also trying to get my head around jobs and listening for events. About
a year ago one of the persons on the list, Oliver, extended extensive help
by providing a job implementation. However since I have been caught up with
other prior things could not test it. Now, although the add on is
successfully added and registered to Ooo, it does not appear to work as it
must. Hence, the debugging attempt. 

 

I was also wondering if it is normal for javamaker to exit with "Result:
99". I have tried in vain to locate the exit codes for javamaker. Any help
in this direction will also be useful.

 

Thanks

 

Cheers

G

 

Gautham Kasinath
Masters Student
School of Computing and Information Science
Edith Cowan University
Mt. Lawley Campus
Perth

 

IM: [EMAIL PROTECTED], [EMAIL PROTECTED]
AOL Screen name: gkasinath42
Mobile: 0433 904 011

Home phone: 61 8 9444 8154

Home Page: http://www.geocities.com/gkasinath
The world is what it is, and we are what we are. - Maria Puzo (Godfather)

 

Reply via email to