Community
Participate
Working Groups
If a facet is applicable to a given module as well as an ear, then by default, if the facet is chosen in the module creation wizard AND the create EAR checkbox is selected, that facet on the EAR should be processed as well. Currently this is not the behavior and the user has to know to select "New" ear to configure the ear. This is a usabilty concern.
Added to Hot List at the request of Sachin Patel and tentatively targetted to 1.0.1 pending triage.
Setting priority to P2.
Bumping up severity on this due to the way JSR88 deployment is implemented in Geronimo. Without this fix two ear projects would have the same id's set in the application.xml after project creation. Since the id's are not initially unique this will cause a failure during deployment. The only assurance is to make sure that the facet is propegated and run on the ear in order to create the geronimo specific deployment plan (geronimo-application.xml) which would contain a unqiue ID for deployment.
+1 on the severity of this bug. We need this problem resolved in order for the Web Services wizard to work on Geronimo server.
This bug should be fixed in the GeronimoFacetInstallDelegate. When the GeronimoFacetInstallDelegate is executed, the J2EE facet will already have been installed and the EAR component created and linked. Thus if an EAR was created, or the J2EEModule already existed and was linked to an EAR (or many EARs), the GeronimoFacetInstallDelegate will be able to add the Geronimo facet to the various EARs. As an aside, there is no way for this to be fixed in a from any of the J2EE facets, because there is no way for the J2EE facet to know what facets are depending on it.
Ok. I wasn't aware that the EAR would already be linked at this point. I just finished implementing this solution, and is acceptable. Thanks!
Resolved in GeronimoFacetInstallDelegate per comments below.
Closing as verified.
Changing OS from Mac OS to Mac OS X as per bug 185991