PM71748: Publishing a Java EE 6 EAR with binary modules fails in looseconfig scenario fails with NoModuleFileException

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:
  
  Publishing a JEE 6 EAR with binary modules fails in looseconfig
  scenario fails with NoModuleFileException
  
  Problem:
  
  This is a general problem which can be reproduced given the
  PlantsByWebSphere example provided by WebSphere Application
  Server.
  
  Steps to reproduce:
  
  1. Use Rational Application Developer for WebSphere Software
  8.0.4.1 with WebSphere Application Server
  2. Extract
  ?WAS8_HOME?\samples\PlantsByWebSphere\pbw-ear\target\pbw-ear.ear
  3. Create a new simple project called lib. Copy lib\pwb-lib.jar
  and PlantsByWebSphere.jar of the extracted files from
  pbw-ear.ear to the project lib
  4. Create a new Enterprise Application Project test
  5. Select project test, open Project Properties, open property
  page Deployment Assembly. Click Add, select Archives from
  Workspace and click Next. Click Add, select pbw-lib.jar and
  PlantsByWebSphere.jar, click OK and click Finish. Press OK
  6. Select project test, open the context menu, select Generate
  Java EE ? Deployment Descriptor Stub
  7. Publish the EAR test to WebSphere Application Server 8.0
  
  Expected Result:
  Application is published without problems
  
  Actual Result:
  Exception NoModuleFileException: A file does not exist for
  module element having uri: PlantsByWebSphere.war
  
  Local fix:
  
  There is no known workaround at this time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There was  an NPE at
  com.ibm.etools.wrd.websphere.core.internal.operations.Abstra
  ctLooseConfigXMIOperationv8Common.addLooseWebArchives(Abstra
  ctLooseConfigXMIOperationv8Common.java:132) that caused a
  publish to fail when using a binary WAR in a non-single root
  structure.
  

Problem conclusion

• The root cause was that the checks that are done in
  com.ibm.etools.wrd.websphere.core.internal.operations.Abstra
  ctLooseConfigXMIOperationv8Common.addLooseModules(IVirtualRe
  ference[]) are not in the proper order.
  
  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

• R850 PSN

     UP