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.

Bug 160549 - [67cat] Wrong host when adding a glassfish remote instance
Summary: [67cat] Wrong host when adding a glassfish remote instance
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-18 14:20 UTC by Eduardo.m Costa
Modified: 2009-09-19 01:30 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 Eduardo.m Costa 2009-03-18 14:20:15 UTC 
[ BUILD # : 200902231810 ]
[ JDK VERSION : 1.6.* ]

Steps to reproduce (assuming glassfish already installed and
working):
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"

Expected behaviour:

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

Current results:

A. Message appears, but wizard stays on "Domain Admin Login Info"
step

B. An invalid server is added and user can't change its port
configuration later
Comment 1 Eduardo.m Costa 2009-03-18 16:57:28 UTC 
Changing to P3, in conformance to http://wiki.netbeans.org/BugPriorityGuidelines
Comment 2 Vince Kraemer 2009-06-08 16:28:29 UTC 
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...
Comment 3 Eduardo.m Costa 2009-06-08 16:58:02 UTC 
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.
Comment 4 Vince Kraemer 2009-06-08 19:30:05 UTC 
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.
Comment 5 Vince Kraemer 2009-09-19 01:30:20 UTC 
The fix would require a pretty substantial rewrite/enhancement of the server node properties page.