[ BUILD # : 200902231810 ]
[ JDK VERSION : 1.6.* ]
Steps to reproduce (assuming glassfish already installed and
1. Go to Services TopComponent
2. Right click on Servers > Add Servers...
3. Select GlassFish V2, Next
4. Click browse and select a valid glassfish installation
5. Change radiobox to "Register remote domain"
6. Click on "next"
7! Type an INVALID server host or port
8! Click on "NEXT", then "finish"
A. User selected an invalid host
* "Invalid host" message
* Go back to "Domain Admin Port Info" step
B. User selected an invalid port
* "Server not running on port X - confirm?" message
* If user does not confirm, go back to "Domain Admin Port Info" step
A. Message appears, but wizard stays on "Domain Admin Login Info"
B. An invalid server is added and user can't change its port
Changing to P3, in conformance to http://wiki.netbeans.org/BugPriorityGuidelines
A couple notes...
1. while a host name may be 'invalid' at the moment, there is nothing that prevents it from becoming valid.
2. while a server may not be detected at a host/port combo at the moment, it is hard to predict whether it will become
So, preventing the user from registering a server because the server is not running on that remote host at this
particular instant is also not desirable...
Please notice I'm not asking to prevent the user from registering a invalid host/port combination. I'm complaining that
there's no "warning" when user tries that. Let's assume I have a server running on a server hostX, port AAAA. If I type
"hostX:AAAb" by mistake, I must remove the wrong server and add a new one from scratch.
BTW: sorry this issue kind of languished. The person that was responsible for reassigning issues to an engineer left
the team. It took a bit of time for the new person responsible for it to clear up the backlog.
The fix would require a pretty substantial rewrite/enhancement of the server node properties page.