IBM Support

PM62289: Source files are not packaged in WEB-INF/classes when exported as an EAR or WAR with export source files selected

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abstract:
    
    Attempts to export an EAR or WAR with the 'export source files'
    option selected results in the source code for a dynamic web
    project not always being included in the resulting archive file.
    
    Problem:
    
    This problem can happen when the project has multiple source
    folders and the metadata for the source folder entries in the
    ?project?/.settings/org.eclipse.wst.common.component is not
    correct.  For example, the Java EE project metadata file has an
    source path entry that does not exist in the workspace.
    
    Local Fix:
    
    Manually editing this metadata file to correct this situation is
    possible; however, this should only be done if advised to do so
    by IBM Rational Application Developer support.  Opening the
    ?project?/.settings/org.eclipse.wst.common.component file and
    removing any source path entries that point to resources that do
    not exist within the workspace.  For example,
    
    Remove:
    ?wb-resource deploy-path='/WEB-INF/classes'
    source-path='/src.main.java'/?
    
    if the source folder 'src.main.java' does not exists.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This problem can happen when the project has multiple source
    folders and the metadata for the source folder entries in
    the ?project?/.settings/org.eclipse.wst.common.component is
    not correct.  For example, the Java EE project metadata file
    has an source path entry that does not exist in the
    workspace.
    

Problem conclusion

  • This issue is fixed in Rational Application Developer
    v8.0.4.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM62289

  • Reported component name

    RATL APP DEV WI

  • Reported component ID

    5724J1901

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-11

  • Closed date

    2012-05-15

  • Last modified date

    2012-05-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

  • R800 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","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 May 2012