[
https://issues.jboss.org/browse/JBIDE-19755?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-19755.
---------------------------------
I verified that this works as described in the blog in JBDS 9.0.0.Beta1 B50 and also JBoss
Tools Beta1. On one occasion after I started a manually added monitor for 8080 and then
started a server, I got the popup saying that a server is already running - I thought it
might be connected to that - the startup poller might in fact poll the monitor local port
instead of the real port. But I couldn't reproduce in several more attempts, so
I'm not sure what it was.
Anyway, after that first glitch everything worked as it should. I even tried using launch
bar to deploy a dynamic web project to a server and that still honored the port monitor so
the internal browser was open with the local port of the monitor (not 8080).
Implement ServerPort portion of wst.servertools API
---------------------------------------------------
Key: JBIDE-19755
URL:
https://issues.jboss.org/browse/JBIDE-19755
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server, upstream
Affects Versions: 4.3.0.Alpha2
Reporter: Rob Stryker
Assignee: Rob Stryker
Labels: new_and_noteworthy
Fix For: 4.3.0.Beta1
WTP has support for port monitoring in it. This is a piece of code that I've
neglected to implement for, oh, 9 years. I think now's the time, since [~bbrodt] has
been asking about it.
Unfortunately, I've been hit by an upstream bug that hinders my progress:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466109
To be clear, I have a proposed patch which works for HTTP monitoring but simply
doesn't function for monitoring the management port due to an upstream bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)