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 113039 - Allow registration of domains by hostname, not just localhost
Summary: Allow registration of domains by hostname, not just localhost
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 5.x
Hardware: All Windows 3.1/NT
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks: 141253
  Show dependency tree
 
Reported: 2007-08-16 19:42 UTC by tamiro
Modified: 2013-11-08 13:48 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
prototype changes for 'default local' case (6.75 KB, text/plain)
2007-08-21 20:15 UTC, Vince Kraemer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tamiro 2007-08-16 19:42:41 UTC
If you use the Tools -> Server Manager -> Add Server 
select SJAS, you cannot enter the full hostname 
for a GF server on your localhost. For the default 
local domain it fills in "localhost" and won't let 
you change it.
To get around that, I selected Register Remote Domain and 
entered the fully qualified hostname of the system on 
which GF resided, which happened to be the local system. 

The server entry was added to the Runtime tree, but 
it isn't functional. You can't drill down into it;
there are no nodes below it.

If you add a Remote Domain that exists and is actually on a 
remote system, the entry does have the Applications, 
Resources, JVMs nodes under it. 

So there is something not right about the special 
case where you want to substitute the fully qualified 
hostname for the local system rather than use localhost.
I wanted to to that for testing web services security 
where the CN in the certificates use the fully qualified 
hostname, so even if the service and client are on 
the local machine if they use the fully qualified host 
name in their URLs it avoids the mismatch you get 
because "localhost" doesn't match the CN.
Comment 1 Vince Kraemer 2007-08-16 21:14:18 UTC
was the local domain (that you were registering as a remote domain) running?

You may be able to do what you want by...

1. shutdown the IDE.
2. edit the .nbattrs file for the installed instance.. this is in you userdir

   $USERDIR/config/J2EE/InstalledServers/.nbattrs

change the URL attribute entry from something like

attr name="url" stringvalue="[/export/home/vbk/v2/pe/6/glassfish]deployer:Sun:AppServer::localhost:4848"

to something like 

attr name="url" stringvalue="[/export/home/vbk/v2/pe/6/glassfish]deployer:Sun:AppServer::myws.sfbay.sun.com:4848"
Comment 2 Vince Kraemer 2007-08-20 17:58:08 UTC
extend registration to include a list with the name of the server instead of localhost in the list of available domains
should help resolve this...
Comment 3 Vince Kraemer 2007-08-21 19:53:09 UTC
*** Issue 100259 has been marked as a duplicate of this issue. ***
Comment 4 Vince Kraemer 2007-08-21 20:15:33 UTC
Created attachment 47003 [details]
prototype changes for 'default local' case
Comment 5 Vince Kraemer 2007-08-21 20:17:34 UTC
Converting this to an enhancement request for the registration wizard.

You should be able to do the registration of a local server domain as a remote now, since I resolved issue 100259.

I want to keep this open to track the use-case that you ran into.

There should be a way to register a domain where the IDE knows the hostname, instead of localhost for the default local,
local and personal domain registration situations.

In the case of the local default, each domain could have TWO entries in the combobox... one listed as localhost:<port>
and the other listed as <hostname>:<port>... in situations where the hostname cannot be determined (is there any), we
should get one entry in the combobox... localhost:<port>.

the UI to support hostname in the other two cases is a bit more confusing and requires more thought.

making the change to support hostnames in the local default domain case is easy, but seems a bit risky for integration
into 6.0... attached diffs of prototype for this change.
Comment 6 Vince Kraemer 2008-04-26 03:35:37 UTC
missed this.  target for 6.5... and make sure this works for v2 and v3
Comment 7 Vince Kraemer 2008-07-31 23:17:12 UTC
this did not make feature freeze.
Comment 8 Vince Kraemer 2008-10-18 03:36:46 UTC
I am going to make this work in the v3 plugin for 7.0
Comment 9 Vince Kraemer 2009-12-08 14:30:22 UTC
this will need to happen post 6.8
Comment 10 TomasKraus 2013-10-10 14:59:39 UTC
Checked into web-main:
----------------------
changeset:   265053:9961561f5bc5
summary:     #113039 - Tooling SDK update.
                       Now supports new features to implement this RFE

This GF Tooling Library update allows to easy scan all IPs on host.
Comment 11 TomasKraus 2013-11-08 13:39:25 UTC
Checked into web-main:
----------------------
changeset:   265057:4a58788b1f2a
user:        Tomas Kraus <TomasKraus@netbeans.org>
date:        Tue Nov 05 16:16:49 2013 +0100
summary:     #113039 - GlassFish registration wizard redesigned

changeset:   265056:b56e63af2926
user:        Tomas Kraus <TomasKraus@netbeans.org>
date:        Wed Oct 23 16:48:42 2013 +0200
summary:     #113039 - Local instance property editor redesigned

changeset:   265055:98abba0257f8
user:        Tomas Kraus <TomasKraus@netbeans.org>
date:        Thu Oct 17 16:43:15 2013 +0200
summary:     #113039 - Host and ports can be specified in server registration wizard

changeset:   266464:8e97b517dcd1
user:        Tomas Kraus <TomasKraus@netbeans.org>
date:        Thu Nov 07 17:01:30 2013 +0100
summary:     GlassFish modules dependency update

changeset:   266463:5918a6328393
user:        Tomas Kraus <TomasKraus@netbeans.org>
date:        Thu Nov 07 16:51:51 2013 +0100
summary:     GlassFish tooling library updated to promoted build 0.3-b054