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 76287 - Installer doesn't recognize Glassfish v2 as valid server
Summary: Installer doesn't recognize Glassfish v2 as valid server
Status: RESOLVED INVALID
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: Sun Solaris
: P3 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-12 15:24 UTC by epesh
Modified: 2006-06-23 16:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
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 epesh 2006-05-12 15:24:10 UTC 
I have two installations of Netbeans 5.5+Enterprise pack. I installed the Sun AS
9, and also Glassfish2-b01. On Windows, adding a server mapped to Glassfish went
fine; however, on Solaris, it didn't recognize Glassfish as a valid Sun AS instance.
Comment 1 Kirill Sorokin 2006-06-21 02:19:28 UTC 
Is it the installer's inability to recognize the server, or you cannot register
it in the IDE?
Comment 2 Kirill Sorokin 2006-06-23 16:02:55 UTC 
I've tried on windows and linux and in both cases glassfish v2 (I used build 08)
was correctly recognized by the installer and integrated with the IDE. Most
probably the AS plugin in the IDE was not capable of working with GFv2 at the
moment EA was released. So it is not an issue at the moment. Resolving as
INVALID, since it's not an issue anymore.
Fell free to reopen if you encounter it a the next release.
Comment 3 Kirill Sorokin 2006-06-23 16:03:52 UTC 
I've tried on windows and linux and in both cases glassfish v2 (I used build 08)
was correctly recognized by the installer and integrated with the IDE. Most
probably the AS plugin in the IDE was not capable of working with GFv2 at the
moment EA was released. So it is not an issue at the moment. Resolving as
INVALID, since it's not an issue anymore.
Fell free to reopen if you encounter it a the next release.
Comment 4 Kirill Sorokin 2006-06-23 16:05:16 UTC 
Reresolving, something must have gone improperly the previous time.