Description Jason Sholl 2010-05-06 17:26:46 EDT

I added a user library to a connector project and the EAR libraries container shows that it added itself and I see JDT cycle dependency errors.

The problem is that this library reference is consumed (as opposed to used).  A check is necessary in J2EEComponentClasspathContainer to ensure consumed type references are not added directly to the classpath (because these references will always point back to the same project rather than the resolved contents).

While I was testing this with some elaborate assembly scenarios, I noticed some NPEs coming from the RemoveComponentFromEnterpriseApplicaitonOperation code; that's what the change in there is for.  While I was investigating that, I steped into the getModuleURI() method a few lines up and discovered the reason this module wasn't being found was because there was no equals or hashcode defined for ClasspathContainerVirtualComponent or its super class; so I created those, and also filtered out the consumed references from this list anyways.

    * 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. 

Without this fix there will be cyclicial classpaths, and NPEs

    * 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 with UI; no JUnit

    * Give a brief technical overview. Who has reviewed this fix? 

see above.  Chuck and Jason have reviewed

    * What is the risk associated with this fix? 

minimal