Community
Participate
Working Groups
Build Identifier: I20101208-1300 After creation of a new Enterprise Application Project 5.0 it does not appear in the Project Explorer view, if it contains already another project. The view should be explicitely refreshed. Reproducible: Always
Please ignore this issue. I've been targeted the project at a server, which does not support Java EE 6. Sorry, my mistake.
Sorry the previous comment refers to the Bug: 334924.
Actually this issue happens only if the project is targeted to JBoss v5.0 server.
The same happened twice during the Java EE smoke test. Once with Dynamic Web 2.5 project and another time with Web 3.0 project. It is not specific to JBoss server adapter. It looks like it happens occasionally. It can lead to confusion for users. Raising to major.
I'm moving this defect to the Java Script team. The behavior, which is very easy to reproduce.. it any "static" web project created once created initially is missing from Project Explorer view, but comes back with refresh. The navigator contribution from JSDT seems to be causing the issue.
Possibly a duplicate or additional case of bug 336991.
Created attachment 189043 [details] proposed patch Proposed patch disables a little more of the CN functionality we inherited from JDT.
Created attachment 189062 [details] updated patch correcting both Script and Project Explorers
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. Breaks a (the?) main usage scenario and establishes a bad first impression. * Is there a work-around? If so, why do you believe the work-around is insufficient? No, it does this for every project that is JavaScript-capable at creation. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Manual testing by creating lots of web, Java, and JavaScript projects. * Give a brief technical overview. Who has reviewed this fix? Alters the behavior in the Project Explorer to refresh, not remove and try to re-add the new project. It also updates the Script Explorer, which would have been broken by that change, to refresh correctly in response. This second aspect has, due to the timing, not yet been reviewed. * What is the risk associated with this fix? Low. It only affects the behavior when adding/creating a JavaScript project.
I see this error when creating a Dynamic Web Project but not a Static Web Project. Refresh fixes the issue. I agree this bug creates a bad impression and should be fixed.
This one is pretty bad. Seems worth the risk.
Verified with 3.2.3-20110216062908 candidate.
.
*** Bug 335557 has been marked as a duplicate of this bug. ***
