2 Replies Latest reply on Apr 16, 2008 12:17 PM by Scott Stark

    EJBTHREE-1291, deployment resolver unification

    Scott Stark Master

      Related to the EJBTHREE-1291 work, there is duplicate logic going on for resolving component endpoints that is spread out across the DeploymentScope
      EjbModuleEjbResolver, EjbModulePersistenceUnitResolver, MessageDestinationResolver and injection handler code.

      I'm proposing either using the generalized DeploymentEndpointResolver spi in integration:
      https://svn.jboss.org/repos/jbossas/projects/integration/trunk/jboss-deployment-spi/src/main/java/org/jboss/deployment/spi/

      or at least mirroring this interface in DeploymentScope so that it can be properly implemented inside of jbossas. The EjbModuleEjbResolver, EjbModulePersistenceUnitResolver, MessageDestinationResolver code would be replaced based on this and the injection handler code should do no resolution as the metadata it receives has to have been resolved with the resolvedJndiName set.