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

Output better exceptions when failing to bind into JNDI

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Major Major
    • EJB 3.0 RC4 - PFD
    • None
    • None
    • None

      Look in the code in EJB3 for anywhere we are binding anything into JNDI (search for bind). Catch any naming exception and wrap it with a new generic NamingException that

      • sets the cause to be the thrown exception
      • sets the exception message to be for example, "Could not bind EJB Foobars local interface", "Could not bind EntityManagerFactory with unitName XXXX to JNDI", etc...

            wdecoste1@redhat.com William Decoste (Inactive)
            patriot1burke@gmail.com Bill Burke (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: