-
Task
-
Resolution: Done
-
Critical
-
None
-
None
-
None
Current "determineResolved*JndiName()" methods, with default logic, are mixing concerns in the Object Model. Resolution of target JNDI names should be extracted.
Following steps to be taken:
- Remove "determine*JndiName()" methods from JBossEnterpriseBeanMetadata and children
- Remove ClassLoader from DeploymentSummary; this is transient anyway
- Remove duplicated fields in EjbDeploymentSummary; these may be obtained via the beanMD instance
- Create a JNDI Policy SPI for ResolveableJndiNameJbossEnterpriseBeanMetadata and ResolveableJndiNameJbossSessionBeanMetadata, denoting that this metadata is capable of resolving JNDI Names.
- Implement the Resolveable* SPI Interfaces in Decorators
- Create Helper Classes to access Resolveable*-type metadata, abstracting the cast from the caller
- Update Unit Tests to use new grammars, allow 0% regression
For integration with AS:
- Create new deployer(s) to decorate metadata with Resolveable* interfaces and JNDI Binding Policies
- Update grammars accordingly
- blocks
-
EJBTHREE-1436 Integrate jboss-metadata (removed "determine" logic from Object Model) with EJB3 Core
- Resolved
- is related to
-
JBMETA-42 Default JNDI naming of EJB3 beans is broken
- Resolved