Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-8689

JNDI namespace doesn't contain beans with inherited business interfaces anymore since 6.0.0.CR1

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 6.0.0.CR1
    • Fix Version/s: None
    • Component/s: EJB, Other
    • Labels:
    • Environment:

      java version "1.6.0_18"

    • Affects:
      Compatibility/Configuration
    • Workaround Description:
      Hide

      specify the implements clause at the class definition of the bean which is to be looked up

      Show
      specify the implements clause at the class definition of the bean which is to be looked up

      Description

      Since 6.0.0.CR1 the lookup of EJBs via jndi doesnt' work anymore if the bean itself doesn't "implement" a business interface but inherits it. I''ve tried this with @Local annotated interfaces and both the old JBoss syntax ("appName/beanName/local") and the newly supported (as of 6.0.0.CR1) portable ones ("java:global/appName/moduleName/beanName!InterfaceFQN").

      "Implements" here means actually specifying an implements statement at the class definition:

      @Local
      interface IBeanA {}

      @Stateful
      class BeanA implements IBeanA {} //lookup of BeanA works

      @Stateful
      class BeanB extends BeanA {} //lookup of BeanB doesn't work

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  wolfc Carlo de Wolf
                  Reporter:
                  tobiasgrundmann Tobias Grundmann
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: