Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321744 - When importing an EAR 6, a Connector module with no DD imported as binary is not listed properly in the display tree.
Summary: When importing an EAR 6, a Connector module with no DD imported as binary is ...
Status: RESOLVED FIXED
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2.2   Edit
Assignee: Scott Huff CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-04 11:36 EDT by Scott Huff CLA
Modified: 2010-08-05 09:30 EDT (History)
2 users (show)

See Also:
cbridgha: review+


Attachments
Patch file alters JavaEEBinaryComponentHelper (1.43 KB, patch)
2010-08-04 11:36 EDT, Scott Huff CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Huff CLA 2010-08-04 11:36:53 EDT
Created attachment 175841 [details]
Patch file alters JavaEEBinaryComponentHelper

Steps to recreate:
-Create an EAR6, adding a connector module with no DD.
-Export the Ear.
-Import the EAR created above:
  -On the Third page of the Ear Import wizard, do not select the connector module, so it is imported as binary.
  -Finish the wizard.
-In the Enterprise Explorer, You will see that the connector project is not properly listed in Ear>Modules>binary 

Investigation:
-The Connector module is properly imported as binary.
-When populating the display tree, when no DD is present, there is no check for connector type modules.

Proposed Solution:
-Proposed patch adds a check for Connectors in the case of no DD present to JavaEEBinaryComponentHelper.getPrimaryRootObject()
Comment 1 Chuck Bridgham CLA 2010-08-04 17:09:31 EDT
approved
Comment 2 Jason Sholl CLA 2010-08-05 09:30:49 EDT
code checked into head for WTP 3.2.2