PM62319: Running an application client with a JAR file added via the deployment assembly page results in a ClassNotFoundException

Rational Application Developer for WebSphere Software 8.5
Rational Software Architect Interim Fix 1 for 8.0.4.2
Rational Software Architect for WebSphere Software Interim Fix 1 for 8.0.4.2

APAR status

• Closed as program error.

Error description

• Abstract:
  
  Attempts to run the WebSphere Application Server v7.0
  Application Client which include a JAR file added via the
  deployment assembly page results classes located in that jar not
  being found.
  
  Problem:
  
  When you want to run a standard Application Client module
  containing a main class via the Run As ? Run Configuration ?
  WebSphere Application Server v7.0 Application Client and have
  referenced classes contained within a JAR file which you
  imported into a separate Utility project, then the classes in
  that imported JAR are not found even if you have referenced the
  Utility project in the deployment assembly page.
  
  You might see errors such as the following:
  
  WSCL0100E: Exception received:
  java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
      at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl
      ....more
  Caused by: java.lang.NoClassDefFoundError:
  com.test.SomeOutsideClass
      at Main.main(Main.java:11)
      ... 27 more
  Caused by: java.lang.ClassNotFoundException:
  com.test.SomeOutsideClass
      at
  java.lang.ClassNotFoundException.?init?(ClassNotFoundException.j
  ava:76)
  
  Local fix:
  
  Add the jar file you imported into the Utility project to the
  'Classpath' tab on the WebSphere Application Server v7.0
  Application Client launch configuration page.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During runtime an application client cannot access a utility
  JAR file, located outside the workspace, that is added via
  the EAR deployment assembly. This is because the loose
  configuration metadata file did not include an entry for
  this utility JAR file.
  

Problem conclusion

• The loose configuration file generation logic has been
  updated to reference utility JAR files that are not located
  in the workspace.  The fix for this APAR is included in
  Rational Application Developer v8.0.4.1.
  

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

• R804 PSN

     UP