Bugzilla – Full Text Bug Listing
| Summary: | 'Deployment Assembly' properties page placing binary module files inside EAR's library directory | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Java EE Tools | Reporter: | Aidyl Kareh <amkareh> | ||||
| Component: | jst.j2ee | Assignee: | Aidyl Kareh <amkareh> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Chuck Bridgham <cbridgha> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | amkareh, ccc, jsholl | ||||
| Version: | unspecified | Flags: | cbridgha:
review+
|
||||
| Target Milestone: | 3.2.3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 184311 [details]
Proposed Patch
Code overrides the handleAddDirective() method to add a quick peek to the binary files that are added so that if they are identified as EJB, Application Client, Web or Connector it sets their deploy path to the root of the EAR.
approve Committed to R3_2_maintenance and HEAD for WTP 3.2.3 and WTP 3.3 |
Build Identifier: WTP 3.2.3 Create an EAR project, open the 'Deployment Assembly' properties page and add an external binary module file (e.g. 'TestWeb.war') ('Add...' -> 'Archives from File System'). It will assemble the binary module file into the EAR's lib folder and does not update the application.xml. The same problem also exists when assembling from an archive in the workspace or variable. The default behavior for EJB JAR files, Application Client JAR files, WARs and RARs should be to place them in the root of the EAR and not in the lib folder. Reproducible: Always