Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-866

WeldBanManagerServiceProcessor is too picky for TorqueBox to integrate with CDI

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 7.0.0.CR1
    • Component/s: CDI / Weld
    • Labels:
      None

      Description

      Weld's WeldBeanManagerServiceProcessor is very picky about deploying up a BeanManager for deployments.

      In TorqueBox's case, we don't have an EEModuleDescription, and we don't end-with .war extension. But we still desire to have the BeanManager deployed. Don't really care if it's registered in JNDI, I don't think; just an MSC Service<T> should keep our stuff happy.

      Against jboss-as#master as of 22-May, we've had to add our own duplication (of sorts) of WeldBeanManagerServiceProcessor to ensure a BeanManager gets deployed. We currently install it at +1 the priority of Weld's, to ensure we don't duplicate deployment.

      If weld's WeldBeanManagerServiceProcessor could happily deploy a BeanManager even if EEModuleDescription isn't present, and the deployment doesn't end with .war, that'd be awesome.

      I'm happy to use some WeldDesireToHaveBeanManager.mark( unit ) marker or whatnot, to indicate our needs.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swd847 Stuart Douglas
                Reporter:
                bob.mcwhirter Bob McWhirter
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: