IBM Support

PM63955: Exporting an EAR file might result in an org.eclipse.jst.jee.archive.ArchiveSaveFailureException

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to export an EAR file results in an
    org.eclipse.jst.jee.archive.ArchiveSaveFailureException
    
    Problem:
    
    When you attempt to export an Enterprise Application project to
    an EAR file then you receive the following error:
    
    org.eclipse.core.commands.ExecutionException: Error
    exportingC:/Projects/MyProject/MyProject.ear at
    org.eclipse.jst.j2ee.internal.archive.operations.
    ComponentExportOperation.execute(Unknown Source)
    at
    org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPa
    usibleOperationImpl$1.run(Unknown
    Source)
    
    Caused by:
    org.eclipse.jst.jee.archive.ArchiveSaveFailureException:
    org.eclipse.jst.jee.archive.ArchiveSaveFailureException:
    java.lang.NullPointerException at
    org.eclipse.jst.j2ee.internal.archive.operations.FlatComponentAr
    chiver.saveArchive(Unknown
    Source)
    
    This error occurs when the workspace is out of sync with the
    local file system.  In most cases a refresh of the projects will
    resolve the error.  In some cases, source control systems have
    created a virtual 'placeholder' entry with no physical file on
    the file system.
    
    Local fix:
    
    There is no known workaround at this time.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This error occurs when the workspace is out of sync with the
    local file system.  In most cases a refresh of the projects
    will resolve the error.  In some cases, source control
    systems have created a virtual "placeholder" entry with no
    physical file on the file system.
    

Problem conclusion

  • If projects which are part of the EAR are out of sync with
    the local file system, they are refreshed before exporting.
    If after refreshing the workspace, they are still out of
    sync with the file system (this can happen when source
    control systems have created a virtual "placeholder" entry
    with no physical file on the file system), an
    org.eclipse.jst.jee.archive.ArchiveSaveFailureException will
    be thrown, with the name of the file that caused the
    failure.
    
    The fix for this APAR is included in Rational Application
    Developer v8.0.4.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM63955

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    804

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-04

  • Closed date

    2012-12-15

  • Last modified date

    2012-12-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATL APP DEV WI

  • Fixed component ID

    5724J1901

Applicable component levels

  • R804 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 December 2012