1. glassfish
  2. GLASSFISH-16358

need better user experience when deploying ear application packaged in archive/directory mixed format


    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: deployment
    • Labels:


      User reported the deployment of their application did not work on windows XP:

      I've encountered the following issue while deploying an ear file on

      Issue: Some of the .uix files turned out to be 0kb after deploying,
      however, this kind of problem did not happen on other J2EE application
      servers such as Weblogic.

      If I unpack the ear file first and deploy it in directory form, this
      issue would not happen.

      Glassfish Version: 3.1

      JDK: 1.6.0_24

      Platform: Windows 7 32 bit/Windows XP 32 bit

      After investigation, the basic issue here is that the ear was not packaged as defined in the Java EE spec. At the top level it was packaged as an ear, but at module level, the modules are in expanded format (not .jar/.war/.rar format). The user verified after the application was packaged as specified in the EE spec, things worked as expected. However, the GlassFish should be enhanced to provide better user experience for this scenario, we could either support this type of packaging as a vendor extension or at least should provide a good error message to give user more clue why it did not work.


        There are no comments yet on this issue.


          • Assignee:
            Hong Zhang
            Hong Zhang
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: