Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
jboss-ejb3-deployer:1.1.2
Description
There are multiple deployers currently which first check whether the container name is set in metadata. If it's not available then the deployer generate a container name, using the deployment unit. This code is duplicated across multiple deployers currently.
Introduce a post processor which sets the container name in the metadata if it's not already set. The other deployers can just get hold of the container name from metadata henceforth.
Attachments
Issue Links
- is incorporated by
-
JBPAPP-4128 Upgrade ejb3-core to 1.3.3
- Closed
- relates to
-
EJBTHREE-2098 ContainerNameMetaDataProcessor generates incorrect container name for EJB packaged in a jar which resides in a .sar
- Resolved