This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | [67cat] Wrong host when adding a glassfish remote instance | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Eduardo.m Costa <_m4c0_> |
Component: | Sun Appserver 9 | Assignee: | Vince Kraemer <vkraemer> |
Status: | NEW --- | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Eduardo.m Costa
2009-03-18 14:20:15 UTC
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 available. 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. |