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 209685 - GlassFish 3.1.2 not registered with new Installation
Summary: GlassFish 3.1.2 not registered with new Installation
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.1.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: TomasKraus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-17 03:39 UTC by bht
Modified: 2013-09-24 12:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bht 2012-03-17 03:39:52 UTC
Product Version: NetBeans IDE 7.1.1 (Build 201203012225)
Java: 1.6.0_30; Java HotSpot(TM) Client VM 20.5-b03
System: Windows XP version 5.1 running on x86; Cp1252; en_NZ (nb)
User directory: C:\Documents and Settings\name\.netbeans\7.1.1

I uninstalled all previous versions of the IDE and GlassFish and installed the full download including GlassFish 3.1.2.

Then I started the IDE and let it import settings from the 7.1 installation that had all patches applied.

In the services window, the server node is empty.
Comment 1 Vince Kraemer 2012-04-17 16:01:28 UTC
Any update on this issue?
Comment 2 TomasKraus 2012-04-19 08:45:05 UTC
I saw similar issue when I was installing netbeans 7.1 on win2003. Glassfish server was not installed and there was no server in Services tab.

Please can you verify 2 things:
  1) Is Glassfish server from nb bundle fully installed and working? Can you manage it manually with asadmin?
  2) Did you see any errors during installation?

In my case missing GF was not related to 7.1 settings import. It happened just because of GF was not installed correctly and it was not working.
Comment 3 TomasKraus 2012-04-19 10:16:28 UTC
Now I did exactly the same what you described:
----------------------------------------------
Product Version: NetBeans IDE 7.1.1 (Build 201203012225)
Java: 1.6.0_31; Java HotSpot(TM) Client VM 20.6-b01
System: Windows 2003 version 5.2 running on x86; Cp1252; en_US (nb)
User directory: C:\Documents and Settings\Administrator.OWMS\.netbeans\7.1.1

I removed NB 7.1, installed 7.1.1 and imported 7.1 settings after 1st start.
I can see both GF servers:
 * GlassFish Server 3+ configured manually in 7.1
 * GlassFish Server 3.1.2 bundled with NB 7.1.1 and installed together with them

At this stage I need more information:
--------------------------------------
1) Can you reproduce this issue any time? If so, how exactly?
2) Is there really some connection to 7.1 setting import?
Comment 4 bht 2012-04-20 06:37:23 UTC
I would suggest that we close this because I don't have any computer where I could let the IDE import older settings. Many thanks.
Comment 5 TomasKraus 2012-04-20 13:08:20 UTC
We were able to reproduce it so I'll keep this bug opened.
But think it's not P2 bug. User can always register his GlassFish manually so this won't cause any serious issues. It's just annoying.

Changing to P3 and we will try to fix it later.
Comment 6 TomasKraus 2012-05-23 08:20:21 UTC
Targeting to next release.
We are actually working on large changes in GlassFish module and P3 fixes should be done after that.
Comment 7 TomasKraus 2012-11-22 16:03:19 UTC
will keep this opened. I already have some plans to modify settings import in next release.
Comment 8 TomasKraus 2013-04-15 14:03:08 UTC
org.netbeans.modules.glassfish.common.registration.AutomaticRegistration has to be rewritten from scratch.

autoregisterGlassFishInstance method rely on some .dtd and .xsd files to detect server version. this is completely wrong.
GlassFish Tooling Library org.glassfish.tools.ide.utils.ServerUtils#getServerVersion method is searching for real version numbers stored in com.sun.appserv.server.util.Version class or for Bundle-Version value in common-util.jar as a fallback option.
It was tested with all known GlassFish servers 3 an 4.

generateUniqueDisplayName should use real server version.

registerServerInstanceFO should relay on GlassfishInstance and GlassfishInstanceProvider code to create and store instance attributes.

I can't do this in 7.3.1 but in 7.4 there will be much more accurate and reliable code.
Comment 9 TomasKraus 2013-07-19 23:22:33 UTC
There is no time to rewrite AutomaticRegistration in 7.4. Postponing for next
release.
Comment 10 TomasKraus 2013-09-24 12:32:58 UTC
Automatic registration code was changed to examine GF installtion files and retrieve real server version instead of using previous crystal sphere based guessing. See Bug# 210747 for details.

I believe it will also resolve this issue.