Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.8.2, 2.0-Alpha2
-
Fix Version/s: 2.0-Alpha3, 2.0.0
-
Component/s: Tool Integrations
-
Labels:None
-
Environment:Netbeans 6.8
Description
While testing new netbeans 6.8 integration, one issue was discovered that netbeans' passes wrong java ee level and serverid chosen in previous project if second project is created right after first project is created.
This is serous problem to icefaces integration as all to-be-selected libraries and GUI options are based on java ee level passed from netbeans.
This issue is confirmed by creating a simple WebModuleExtender. This looks like a timing issue in netbeans.
Netbeans' JSF framework seems to try to work around this issue by passing swing event back/forth so that selecting JSF framework in wizard is very non-responsive.
This is serous problem to icefaces integration as all to-be-selected libraries and GUI options are based on java ee level passed from netbeans.
This issue is confirmed by creating a simple WebModuleExtender. This looks like a timing issue in netbeans.
Netbeans' JSF framework seems to try to work around this issue by passing swing event back/forth so that selecting JSF framework in wizard is very non-responsive.
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Liming Wu [ liming.wu ] |
Salesforce Case | [] | |
Component/s | Tool Integrations [ 10017 ] |
Salesforce Case | [] | |
Description |
While testing new netbeans 6.8 integration, one issue was discovered that netbeans' passes wrong java ee level and serverid chosen in previous project if second project is created right after first project is created. This is serous problem to icefaces integration as all to-be-selected libraries and GUI options are based on java ee level passed from netbeans. This issue is confirmed by creating a simple WebModuleExtender. This looks like a timing issue in netbeans. Netbeans' JSF framework seems to try to work around this issue by passing swing event back/forth so that selecting JSF framework in wizard is very non-responsive |
While testing new netbeans 6.8 integration, one issue was discovered that netbeans' passes wrong java ee level and serverid chosen in previous project if second project is created right after first project is created. This is serous problem to icefaces integration as all to-be-selected libraries and GUI options are based on java ee level passed from netbeans. This issue is confirmed by creating a simple WebModuleExtender. This looks like a timing issue in netbeans. Netbeans' JSF framework seems to try to work around this issue by passing swing event back/forth so that selecting JSF framework in wizard is very non-responsive. |
Summary | work around netbeans' bug which passes wrong java ee level | Sequential creation of new projects in NetBeans 6.8 can result in incorrect JEE version being set. |
Salesforce Case | [] | |
Affects Version/s | 1.8.2 [ 10190 ] | |
Priority | Major [ 3 ] | Minor [ 4 ] |
Attachment | org-netbeans-modules-web-frameworks-dummy.nbm [ 12194 ] |
Salesforce Case | [] | |
Fix Version/s | 2.0-Beta [ 10231 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Fix Version/s | 2.0-Alpha3 [ 10032 ] | |
Fix Version/s | 2.0-Beta [ 10231 ] | |
Resolution | Fixed [ 1 ] |
Fix Version/s | 2.0.0 [ 10230 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
To demostrate this issue, I create a very simple webmoduleextender called dummy web framwork module as nbm. Install it and try to create a couple of web project with dummy framework selected. For each project, you may try to switch between glassfish 3/JavaEE 6 and tomcat 6, and also check log to see if dumped log such as ***** update() j2eeLevel = 1.6 or 1.5 maches you selected in project wizard. You will understand what is this issue is about.
Correct j2eeLevel/serverID are import for this release because we ships icefaces 1.8.2 (JSF 1.1/1.2 JavaEE5/1.4) and icefaces 2.0-alpha2 (on JSF 2.0/JavaEE6) with it and this integration is intended to support both of them.