Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-832

Remote EJBs can be resolved by name

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 1.1.0.Final
    • Fix Version/s: None
    • Component/s: Resolution
    • Labels:
      None

      Description

      You can lookup Remote EJBs via BeanManager based on name. Remote EJBs should not be registered as Beans.

      Failed tests:
      runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest)
      runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest)
      runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest)

      tests: https://github.com/opentck/javaee_cdi_ejb

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            alesj Ales Justin added a comment -

            Aslak, is this still an issue?

            Show
            alesj Ales Justin added a comment - Aslak, is this still an issue?
            Hide
            aslak Aslak Knutsen added a comment -

            still seems to be a issue with 7.1.0.Final:

            Failed tests:   runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.stateful.RemoteViewStatefulEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1>
              runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.singleton.RemoteViewSingletonEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1>
              runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.stateless.RemoteViewStatelessEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1>
            

            Show
            aslak Aslak Knutsen added a comment - still seems to be a issue with 7.1.0.Final: Failed tests: runTest(org.opentck.javaee.cdi_ejb.deployments.stateful.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.stateful.RemoteViewStatefulEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1> runTest(org.opentck.javaee.cdi_ejb.deployments.singleton.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.singleton.RemoteViewSingletonEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1> runTest(org.opentck.javaee.cdi_ejb.deployments.stateless.remoteview.WarDeployedNamedAccessTest): No beans should be found: [Session bean [class org.opentck.javaee.cdi_ejb.deployments.beans.stateless.RemoteViewStatelessEJB with qualifiers [@Any @Default @Named]; local interfaces are []] expected:<0> but was:<1>
            Hide
            alesj Ales Justin added a comment -

            Stuart, can you please have a look?

            Show
            alesj Ales Justin added a comment - Stuart, can you please have a look?
            Hide
            swd847 Stuart Douglas added a comment -

            I don't think this is a big deal, and is not really worth fixing at the moment, unless someone else wants to take it.

            Show
            swd847 Stuart Douglas added a comment - I don't think this is a big deal, and is not really worth fixing at the moment, unless someone else wants to take it.
            Hide
            mkouba Martin Kouba added a comment -

            Remote EJBs should not be registered as Beans

            Actually I see no such restriction in the spec - only that remote interfaces are not included in the set of bean types.

            Note that we already agreed (WELD-364) that observer methods may be methods of a remote interface. So theoretically the lookup is ok and the bean returned should only have one bean type: java.lang.Object. Of course the question is whether it makes sense to have such a useless bean.

            Show
            mkouba Martin Kouba added a comment - Remote EJBs should not be registered as Beans Actually I see no such restriction in the spec - only that remote interfaces are not included in the set of bean types. Note that we already agreed ( WELD-364 ) that observer methods may be methods of a remote interface. So theoretically the lookup is ok and the bean returned should only have one bean type: java.lang.Object . Of course the question is whether it makes sense to have such a useless bean.
            Hide
            jharting Jozef Hartinger added a comment -

            Although meaningless, there is no requirement to ignore session beans whose only bean type is java.lang.Object.

            Show
            jharting Jozef Hartinger added a comment - Although meaningless, there is no requirement to ignore session beans whose only bean type is java.lang.Object.

              People

              • Assignee:
                mkouba Martin Kouba
                Reporter:
                aslak Aslak Knutsen
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development