Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0.ALPHA2
    • Component/s: None
    • Labels:
      None

      Description

      For instance, I'd been expecting JBossEjbResolver to itself be an MC bean, where the EjbReferenceResolver would be an injected instance member.

      Like I do in ejb3-mc-int:

      ...declares the EjbReferenceResolver impl:
      <bean name="org.jboss.ejb3.EjbReferenceResolver" class="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolver">
      <constructor factoryClass="org.jboss.ejb3.common.resolvers.spi.EjbReferenceResolverFactory"
      factoryMethod="newInstance">
      <parameter>org.jboss.ejb3.common.resolvers.plugins.FirstMatchEjbReferenceResolver</parameter>
      </constructor>
      </bean>

      ...injects the EjbReferenceResolver into something that uses it.
      <bean name="org.jboss.ejb3.EjbReferenceAnnotationPlugin"
      class="org.jboss.ejb3.mcint.metadata.plugins.EjbReferenceAnnotationPlugin">
      <constructor>
      <parameter><inject bean="org.jboss.ejb3.EjbReferenceResolver" /></parameter>
      </constructor>
      </bean>

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                alesj AleŇ° Justin
                Reporter:
                pmuir Pete Muir
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: