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 143009 - [65cat]On Creation of a Java EE Web Project the ide cannot set the already registerd GlassFish v3 Prelude as the target server
Summary: [65cat]On Creation of a Java EE Web Project the ide cannot set the already re...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: blueprints (show other bugs)
Version: 6.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Yutaka Yoshida
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-06 09:09 UTC by rajivderas
Modified: 2013-02-13 10:20 UTC (History)
3 users (show)

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 rajivderas 2008-08-06 09:09:06 UTC 
steps to reproduce:

1) Go to "Services" window and on "Servers" node right click and select "Add Server"
2) In "Add Server Instance" wizard select "GlassFish v3 Prelude" and click next
3) Set the "Server Location" if not download download it and click next and give the "Domain Location" and finish the
wizard.
4) Now Click create "New Project"
5) In "New Project" wizard select "sample->Java EE" from "Categories" and "JSF JPA CRUD" from "Projects" list
6) Click Next and then finish.
 The warning message appears with the message "Re solve Missing Server Problem"
This happens only if i have the "GlassFish v3 Prelude" server registered but if i have the "GlassFish v2" also
registered this warning want appear and it will automatically select "GlassFish v2" as the default server for the newly
created application. If ONLY "GlassFish v3 Prelude" server is registered then it would not select its server
automatically for the newly created application.
This can be viewd by right clicking on the newly created application node and selection properties and then clicking
"Run" category the "Server" drop down list is not selected with the already registered "GlassFish v3 Prelude" server but
for "GlassFish v2" it is selected.
Comment 1 David Konecny 2008-08-06 09:17:26 UTC 
Petr, do you wanna have a look at this one?
Comment 2 Petr Hejl 2008-08-06 10:00:58 UTC 
I think every sample comes with predefined server type - it is J2EE (glassfish v2) for this one, while glassfish v3 is
gfv3. Not sure whether we want to solve it somehow (making this sample gfv3 sample?).
Comment 3 Vince Kraemer 2008-08-06 17:16:43 UTC 
I will try to create a fix for this.... It may require some changes in the j2eeserver layer, though.
Comment 4 Vince Kraemer 2008-08-13 23:53:51 UTC 
it looks like we could extend the search, by changing the semantics of Deployment.getInstancesOfServer(String id)... i
don't know if that is safe yet.
Comment 5 Vince Kraemer 2008-08-14 00:06:39 UTC 
it looks like changing the semantics of getInstancesOfServer is not safe.

So, it looks like we need a new API (on Deployment... I guess) and the OpenHook for various project types would need to
be extended to use it.
Comment 6 Petr Hejl 2008-08-14 11:05:29 UTC 
The problem is not with j2ee server api or gfv3 afaik. The trouble is the infrastructure for samples. So far samples are
just packed projects. Such projects has its configured server which is GFv2 or Tomcat. So there should be either
multiple projects for single sample (selected on background by requirements) or wizard for samples should handle this cases.

Note that sample infrastructure has other caveats such as db requirements etc.