Bug 309278 - Poll for the debug target
Summary: Poll for the debug target
Status: ASSIGNED
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Michael Rennie CLA
QA Contact: Simon Kaegi CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-15 05:10 EDT by Michael Schneider CLA
Modified: 2010-04-27 12:41 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Schneider CLA 2010-04-15 05:10:55 EDT 
Currently, when starting an application which runs a rhino, one has to wait until the debugger is started, then can connect to the target using the JavaScript launch target. If connecting too early, a "Connection refused" dialog is shown.

It would be cool if the JavaScript launch configurations would poll for a certain time for the debug target to start listening for incoming debugger connections.

Doing so would allow to restart the actual launch target and the JavaScript debugger launch target at the same time, for example when running unit tests.
Comment 1 Michael Rennie CLA 2010-04-15 11:13:05 EDT 
This is a really good idea, originally we followed the JDT debug remote debug launcher with the attitude "if nothing listening just die", but I agree we could do better. 

I think it would be good to expose the polling timeout as an option on the launch configuration as well, that way users have finite control of how long to wait for a debugger to start.
Comment 2 Michael Rennie CLA 2010-04-27 12:41:27 EDT 
no time for M7...