glassfish
  1. glassfish
  2. GLASSFISH-17376

Tests in appclient failed after moving ejb ref mapping from sun-application.xml to application.xml lookup-name

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.2, 4.0
    • Component/s: ejb_container
    • Labels:
      None

      Description

      the tests:
      application.xml declares ejb-ref to a remote EJB, deployed separately as a ejb module,

      if mapping the ejb ref with jndi-name in sun-application.xml to its portable global jndi name, it works; After moving the mapping to lookup-name in application.xml, the test failed.

      there are 3 similar tests: from appclient, 2 other from war. Only the appclient one failed.

      assembly/appres/appclientejb

        Activity

        Hide
        Cheng Fang added a comment -

        looks like the thread context classloader is not properly set in this particular case in EjbNamingReferenceManagerImpl

                } else if (!ejbRefDesc.hasJndiName() && ejbRefDesc.hasLookupName()) {
        
        Show
        Cheng Fang added a comment - looks like the thread context classloader is not properly set in this particular case in EjbNamingReferenceManagerImpl } else if (!ejbRefDesc.hasJndiName() && ejbRefDesc.hasLookupName()) {
        Hide
        Cheng Fang added a comment -

        Committed revision 50370. to trunk

        Committed revision 50371 to 3.1.2 branch.

        Show
        Cheng Fang added a comment - Committed revision 50370. to trunk Committed revision 50371 to 3.1.2 branch.

          People

          • Assignee:
            Cheng Fang
            Reporter:
            Cheng Fang
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: