PM70775: Running a WAR file might results in a 'A file does not exist' error

Rational Application Developer for WebSphere Software 8.5.1
Rational Application Developer Standard Edition, Version 8.0.4.2

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Attempts to run a WAR file on WebSphere Application Server
  published via Rational Application Developer might result in an
  'A file does not exist' error.
  
  Problem:
  
  When trying to run your WAR file on a WebSphere Application
  Server which is published via Rational Application Developer and
  using the 'Run server with resources within the workspace'
  publishing option, you receive an error similar to the
  following:
  
  [7/26/12 17:23:50:306 CDT] 0000000f TreeBuilder W ODCF0002E:
  Exception: A file does not exist for module element having uri:
  xxxx.war.
  [7/26/12 17:23:50:337 CDT] 0000001c AdminHelper A ADMN1008I: An
  attempt is made to start the xxxxxxApp application. (User ID =
  xxxxx)
  ........
  [7/26/12 17:23:50:353 CDT] 0000001c ApplicationMg E WSVR0100W:
  An error occurred initializing, xxxxxxxApp
  org.eclipse.jst.j2ee.commonarchivecore.internal.exception.NoModu
  leFileException:
  A file does not exist for module element having uri: xxxx.war
  at
  org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleRefIm
  pl.checkType(ModuleRefImpl.java:497)
  ........
  
  This error does not happen when using the 'Run server with
  resources on server' option.
  
  Local fix:
  
  Use the publishing option 'Run server with resources on server'.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a binary archive is added to the deployment assembly
  and it is outside of the workspace then it will fail to
  publish because the archive will not be copied to the
  metadata directory.
  

Problem conclusion

• The fix is to ensure that when the binary archive is not in
  the workspace then it will also check the file system.
  
  The fix for this APAR is included in Rational Application
  Developer v8.0.4.2.
  

Temporary fix

Comments

APAR Information

• 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

• R801 PSN

     UP