This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Q:How to debug a custom bean...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 04, 2006
02:23 AM
Q:How to debug a custom bean...
Hi,
I'm new to Installshield MP and wonder how to perform a debugging session of a custom bean for example in Eclipse. I didn't find any information related to this in the documentation or this forum...
However, it might be clear by concept to long-time IS MP developer. Can someone please point me to the related information?
Thanks in advance & best regards
Heiko Ott
I'm new to Installshield MP and wonder how to perform a debugging session of a custom bean for example in Eclipse. I didn't find any information related to this in the documentation or this forum...
However, it might be clear by concept to long-time IS MP developer. Can someone please point me to the related information?
Thanks in advance & best regards
Heiko Ott
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 04, 2006
03:35 PM
this is how I usually do it:
1) kick off your installer from the commandline with the debug parameters
eg.
java -Xdebug -Djava.complier=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555 -jar setup.jar
note: choose a port that is not in use
2) from eclipse
a) select the debug perspective
b) add a break point in the required class
c) select menu item "run > debug"
d) select "Remote Java Application" item
e) select new, and enter "localhost" and the port you specified above
f) click debug
g) step through your code
note: this is for installer runtime, not build time
Good luck,
James.
1) kick off your installer from the commandline with the debug parameters
eg.
java -Xdebug -Djava.complier=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5555 -jar setup.jar
note: choose a port that is not in use
2) from eclipse
a) select the debug perspective
b) add a break point in the required class
c) select menu item "run > debug"
d) select "Remote Java Application" item
e) select new, and enter "localhost" and the port you specified above
f) click debug
g) step through your code
note: this is for installer runtime, not build time
Good luck,
James.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2006
05:28 AM
Hi James,
thanks for your help!
You approach makes sense to me - I can connect the debugger and everything seems to be ok. However the breakpoints in my beans are ignored. Breakpoints in customcode are active.
Do you have any idea what's going on?
Thanks in advance!
Heiko
thanks for your help!
You approach makes sense to me - I can connect the debugger and everything seems to be ok. However the breakpoints in my beans are ignored. Breakpoints in customcode are active.
Do you have any idea what's going on?
Thanks in advance!
Heiko
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 05, 2006
03:02 PM
Hi Heiko,
did you compile your classes with debug information?
eg. if you are using ant, something like:
...
James.
did you compile your classes with debug information?
eg. if you are using ant, something like:
...
James.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 09, 2006
07:25 AM
Hi James,
yes - of course. The eclipse debugger gives feedback if the line numbering information is missing...
I'll go thru it with a J developer who's now back from vacation.
Thanks for your support so far!
Regards,
Heiko
yes - of course. The eclipse debugger gives feedback if the line numbering information is missing...
I'll go thru it with a J developer who's now back from vacation.
Thanks for your support so far!
Regards,
Heiko