Community
Participate
Working Groups
The use case for a USED reference that is not binary has been implemented but the non-javadoc comments indicate the use case has not been tested. Playing with the API I've discovered that it works properly *except* that JEEHeirarchyExportParticipant's code misidentifies my new custom example reference type as a child module. The reason it does this is because it does not check anything about the reference type, class, etc, but rather only checks if the reference's enclosing project is also a jee project. Once marked as a child module, the enclosing framework later tries to found an IModule for it and obviously cannot. I suggest the heirarchy participant check the classes to make sure the reference types are j2ee components or j2ee archive components or ear components.
Created attachment 184126 [details] Suggested Patch This patch verifies that the virtual component was made with one of the jeetools' component factories, and thus is a true jee component (and not just a virtual component who's getProject() method returns a jee project).
Passing to Chuck for approval to get it into maintenance, and to avoid branching ;)
Hey Chuck: Any chance you can approve this as well?
looks good
Committed and released to 3.3.1 and 3.4.0
