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.
The typical use-case is that you typically use the AS version as the name of the node (i.e. "GlassFish v1") and after adding a domain you want to have consistent naming ("GlassFish v1 - domain1" and "GlassFish v1 - domain2").
*** Issue 116331 has been marked as a duplicate of this issue. ***
*** Issue 110806 has been marked as a duplicate of this issue. ***
*** Bug 173572 has been marked as a duplicate of this bug. ***
*** Bug 129071 has been marked as a duplicate of this bug. ***
*** Bug 215103 has been marked as a duplicate of this bug. ***
Backend is now able to change the server name: web-main a85784962fbe.
UI and common api part still missing.
Integrated into 'main-silver', will be available in build *201309260002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/a85784962fbe User: Petr Hejl <phejl@netbeans.org> Log: #93196 - Provide a way to rename a server node
Fixed in web-main d027bc6cfac0.
Though as glassfish is using a common server api it has to solve it on its own. I would strongly recommend to migrate it to j2eeserver api. I filed issu #236417 and issue #236418.
Integrated into 'main-silver', will be available in build *201309270002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/d027bc6cfac0 User: Petr Hejl <phejl@netbeans.org> Log: #93196 - Provide a way to rename a server node
Server node name is unique and is used as key attribute. Renaming it may cause problems with already running tasks.
*** Bug 236417 has been marked as a duplicate of this bug. ***