Community
Participate
Working Groups
Build Identifier: WTP 3.2.2 There are some issues with how the Project Explorer handles module archives that are placed in the library directory folder. Currently the Project Explorer shows this archives in both the 'Library Directory' and the 'Modules' node. These should be displayed only under the 'Library Directory' node if their deploy path is set to the library directory since they should not be considered modules in this case. Also, if you select 'Java EE Tools' -> 'Generate Deployment Descriptor Stub', you will see that the module archives that are in the library directory folder are also added as modules on the application.xml file. Steps to Reproduce: 1) Create an EAR project with no DD. 2) Go to the EAR's 'Deployment Assembly' page and select 'Add...' -> 'Archives From File System' -> select an EJB project jar. Make sure that the deploy path is set to the library directory folder. Accept the changes and close the 'Deployment Assembly' page (You will see the problems in the Project Explorer). 3) Select the EAR and right-click 'Java EE Tools' -> 'Generate Deployment Descriptor Stub' (you will the the lib files added as modules) Reproducible: Always
Created attachment 177895 [details] Proposed Patch The attached patch updates the code so that module archives in the library directory are not considered modules and are treated correctly by the Project Explorer and when adding modules to the EAR model. This patch also adds code to clear the archives cache (changes to EarModuleDependenciesPropertyPage class) since there was a timing issue which caused stale archive data to be used by the AddComponentToEnterpriseApplicationOp class.
approve.
* 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. We are currently displaying module archive (EJB/Application Client jars) which have their deploy path set to the library directory folder under the 'Modules' node in the Project Explorer and are also adding them as modules to the application.xml when generating the DD. This behavior is incorrect since this files should be treated as utilities and not modules. * Is there a work-around? If so, why do you believe the work-around is insufficient? No. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Tested through UI. * Give a brief technical overview. Who has reviewed this fix? The attached patch updates the code so that module archives in the library directory are not considered modules and are treated correctly by the Project Explorer and when adding modules to the EAR model. This patch also adds code to clear the archives cache (changes to EarModuleDependenciesPropertyPage class) since there was a timing issue which caused stale archive data to be used by the AddComponentToEnterpriseApplicationOp class. This patch has been reviewed by Chuck and Jason. * What is the risk associated with this fix? Low.
approved
code checked into head for wtp 3.2.2 and 3.3
