Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-2002

Nointerface view binding to a jndi name with non-existent subcontext can lead to NameNotFoundException

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EJB3_1 1.0.3
    • None
    • nointerface
    • None
    • nointerface:1.0.0-alpha-4

      A stateful bean with a no-interface view deployed through an .ear runs into a NameNotFoundException while trying to bind to something like the following:

      A/b/no-interface

      The reason is the StatefulNoInterfaceViewJNDIBinder while binding, does not create any relevant sub-contexts. The fix is to use org.jboss.naming.Util.bind() API to bind to JNDI. This API internally creates any relevant sub-contexts.

              jaikiran Jaikiran Pai (Inactive)
              jaikiran Jaikiran Pai (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: