Application Server 3  4  5 and 6
  1. Application Server 3 4 5 and 6
  2. JBAS-7004

EJB3Deployer does not use the correct MC API and ends up picking irrelevant deployments

    Details

    • Type: Bug Bug
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: JBossAS-5.1.0.GA
    • Fix Version/s: 6.0.0.M1
    • Component/s: EJB
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      EJB3Deployer currently uses the addInput(MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME); API of MC deployers and expects that it will be invoked only if the MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME attachment is available in the deployment unit. However, this is not the right API to use. This results in the EJB3Deployer being invoked for irrelevant deployments as shown here http://lists.jboss.org/pipermail/jboss-development/2009-June/014560.html

      The MC forum thread explaining the API usage is here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=156725

        Gliffy Diagrams

          Activity

          Hide
          jaikiran pai added a comment -

          The org.jboss.ejb3.deployers.Ejb3Deployer has been changed to use the correct MC API for setting JBossMetadata as a requirement.

          Show
          jaikiran pai added a comment - The org.jboss.ejb3.deployers.Ejb3Deployer has been changed to use the correct MC API for setting JBossMetadata as a requirement.

            People

            • Assignee:
              jaikiran pai
              Reporter:
              jaikiran pai
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development