Bug 159740 - ExternalServerBehaviour for external servers on localhost which are already running
Summary: ExternalServerBehaviour for external servers on localhost which are already r...
Status: NEW
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Gorkem Ercan CLA
QA Contact: Tim deBoer CLA
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-10-04 11:40 EDT by David Black CLA
Modified: 2007-12-16 13:24 EST (History)
0 users

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 David Black CLA 2006-10-04 11:40:55 EDT 
The current setupLaunch behaviour of
org.eclipse.jst.server.generic.core.internal.ExternalServerBehaviour is an
issue in the following circumstances. We have a "remote"/external serverType
defined. It is handy to be able to create a server based on this which is
actually running on localhost, but is controlled outside of Eclispe/WTP. So the
start behaviour is a no-op. But ExternalServerBehaviour.setupLaunch calls
GenericServerBehaviour.setupLaunch which checks to see if the port is in use if
the server is localhost, and displays an error message if it is. It should be possible to define a flag that overrides this behaviour i.e. allows external servers on localhost that are already running, doesn't check if the port is in use. The alternative to a flag is maybe a 'ExternalServerConnectBehaviour' that extends ExternalServerBehaviour (which is what we have done in the interm).
Comment 1 Tim deBoer CLA 2007-12-16 13:24:18 EST 
This is a valid request, but since there has been no resource to work on this I am adding the helpwanted keyword to request help from the community.