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.
I've tried to create an j2ee application using registered GlassFish server. Reproduction: 1. new project | j2ee application 2. change name 3. press Finish Result: a few exceptions were thrown, the new project dialog was not closed
Created attachment 29134 [details] ide log
Caused by un-implemented application-client DD handling in AS plugin, moving there. BTW: there are few workarounds: -use JBoss instead of AS for now -uncheck "Create Application Client module" checkbox in the new EAR wizard
I'm testing an ejb 3.0 tutorial, I cannot use the workarounds :).
But nice try, wasn't it :) "Create Application Client module" checkbox is not checked by default. IDE: [6.3.06 17:49] Committing Files started Checking in PanelOptionsVisual.form; /cvs/j2ee/earproject/src/org/netbeans/modules/j2ee/earproject/ui/wizards/PanelOptionsVisual.form,v <-- PanelOptionsVisual.form new revision: 1.1.16.1.2.3; previous revision: 1.1.16.1.2.2 done Checking in PanelOptionsVisual.java; /cvs/j2ee/earproject/src/org/netbeans/modules/j2ee/earproject/ui/wizards/PanelOptionsVisual.java,v <-- PanelOptionsVisual.java new revision: 1.1.16.1.2.3; previous revision: 1.1.16.1.2.2 done IDE: [6.3.06 17:49] Committing Files finished Real issue is in AS plugin - see stack trace.
Why wasn't this tested before the check-in of app client? oh well.
Since the default was changed, I think this is a P2 now.
per Petr J's comment
was tested with sources from appclient branch. And attached patch, whose base works for me for more than half of a year, is made from that...
Created attachment 29140 [details] proposed patch
*** Issue 73320 has been marked as a duplicate of this issue. ***
this appears to be fixed in release55 branch. pcw: please comment and correct me or mark as fixed...
There was a 12-hour window on Monday, March 6th when the appclient project was initially merged into the release55 branch, where I can imagine the build was in such a state that this bug might occur, though I'm not exactly sure how. However, on that Monday afternoon, I committed a series of changes that should prevent this situation from happening and as of this writing, I cannot reproduce this behavior. Therefore, I'm closing this bug as FIXED. On encountering any future exceptions in this area (or any other part of sunddui, for that matter), please file new bugs with appropriate particulars.
verified