glassfish
  1. glassfish
  2. GLASSFISH-13556

Deployment of ear file fails on b19, b20

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: 3.1
    • Fix Version/s: not determined
    • Component/s: cdi
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      13,556

      Description

      The soon-to-be-attached test case fails to deploy on build 20.

      The test case consists of an ear file. The ear file has a war file in it with a
      Servlet. The ear file also contains two EJBs, one of which extends the other.
      I believe that it is a valid deployment archive.

      1. issue13556.tar.gz
        5 kB
        ljnelson
      2. issue13556-no-cdi.tar.gz
        4 kB
        ljnelson
      3. stack.txt
        38 kB
        ljnelson
      4. stack2.txt
        11 kB
        ljnelson

        Activity

        Hide
        ljnelson added a comment -

        If you remove the beans.xml file--thus making this .ear file be a
        straightforward Java EE 5 ear--deployment succeeds, but the first hit to the
        servlet fails. I will attach this stack.

        Show
        ljnelson added a comment - If you remove the beans.xml file--thus making this .ear file be a straightforward Java EE 5 ear--deployment succeeds, but the first hit to the servlet fails. I will attach this stack.
        Hide
        ljnelson added a comment -

        Created an attachment (id=4932)
        A stack showing what happens when you remove the beans.xml file from the simplified Maven project, build and deploy it, and attempt to access the successful deployment.

        Show
        ljnelson added a comment - Created an attachment (id=4932) A stack showing what happens when you remove the beans.xml file from the simplified Maven project, build and deploy it, and attempt to access the successful deployment.
        Hide
        ljnelson added a comment -

        Pilot error in here; going to correct it and retest. Duplicate entries for
        caturgiator-ejb. My apologies....

        Show
        ljnelson added a comment - Pilot error in here; going to correct it and retest. Duplicate entries for caturgiator-ejb. My apologies....
        Hide
        ljnelson added a comment -

        Mortally embarrassed. Apologies for wasting folks' time.

        A duplicate jar entry in the top level of the ear project and the lib directory
        was causing all of the issues.

        (Does bring up an issue, though: if I have two EJB modules at the top level of
        the ear file, is it guaranteed by specification that one of them will be able to
        extend classes in the other?)

        Show
        ljnelson added a comment - Mortally embarrassed. Apologies for wasting folks' time. A duplicate jar entry in the top level of the ear project and the lib directory was causing all of the issues. (Does bring up an issue, though: if I have two EJB modules at the top level of the ear file, is it guaranteed by specification that one of them will be able to extend classes in the other?)
        Hide
        ljnelson added a comment -

        Changed status to INVALID since this bug was due to pilot error.

        Show
        ljnelson added a comment - Changed status to INVALID since this bug was due to pilot error.

          People

          • Assignee:
            Sivakumar Thyagarajan
            Reporter:
            ljnelson
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: