Uploaded image for project: 'Geronimo'
  1. Geronimo
  2. GERONIMO-2142

EJB Refs to EJB in parent module often fail

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.1
    • 1.1.1
    • deployment, OpenEJB
    • Security Level: public (Regular issues)
    • None

    Description

      In OpenEJBReferenceBuilder:

      createEJBLocalRef and createEJBRemoteRef accept a targetConfigId argument.

      Then they often call getMatch or getImplicitMatch and don't use the targetConfigId. As a result, the current module's ID is always used as the targetConfigId:

      context.findGBeans(new AbstractNameQuery(context.getId(), ...

      This means that the query will never match EJBs in a parent of the current configuration. It should be changed to use the targetConfigId instead of the current module's ID.

      This does not come up if a pattern element is used in the mapping, though that mapping strategy runs into a different 1.1 bug (ClassCastException on org.openejb.proxy.ProxyInfo)

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            djencks David Jencks
            ammulder Aaron Mulder
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment