PM92886: CUSTOM JAVA CODE (E.G. ADAPTERS, CUSTOM LOGIN MODULES) ADDED TO WORKLIGHT PROJECT DO NOT WORK ON THE DEVELOPMENT SERVER

APAR status

• Closed as program error.

Error description

• When creating a Worklight project with an adapter that runs java
  code, the java code does not work and the adapter invocation
  will fail.
  When creating a Worklight project with a custom login module,
  the Worklight development server won't start and complains about
  missing classes. (ClassNotFoundException)
  

Local fix

• To work around the issue:
  1. Change something in the authenticationConfig.xml (adding a
  space is sufficient)
  2. Perform a "Project -> clean"
  3. Restart the development server
  Those three steps should be done when changing the java code (of
  the custom classes) or when changing files under /server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Developers building applications which use custom java code  *
  * and who test their projects in a development environment.    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Invocation of an adapter procedure (from within Worklight    *
  * Studio) which executes java code will fail without a clear   *
  * error message.                                               *
  * The development server won't start-up when the               *
  * authenticationConfig.xml contains custom login module(s).    *
  * The error (in the server log) will contain                   *
  * "ClassNotFoundException"s                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some cases (custom login modules, adapters executing java),
  there is a need to include java classes on the server side of a
  Worklight project. It is possible to do so by creating those
  classes under the server/java folder of a Worklight project. The
  classes should find their way to the project's war file during a
  Studio build. The problem is that starting from the second
  Studio build, the WAR file does not contain those classes, which
  means that the java functionality of those classes won't work on
  the server. In the case of a custom login module, it will
  prevent the server from starting up. In case of the adapters
  java code, the adapter procedure which invokes the java code
  will fail.
  

Problem conclusion

• The code has been altered to prevent the deletion of the class
  files after the WAR file is built.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 6.0.0.1.
  A fix is available in 6.0.0.0-IF201307011413 and later.
  

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

  WORKLIGHT CONSU

• Fixed component ID

  5725I4301

Applicable component levels

• R600 PSY

     UP