PM34351: EJBDeploy fails with 'colliding project name error' if the EAR includes EJB JARs with the same name but in different folders

Rational Application Developer for WebSphere Software, Version 7.5.5.4

APAR status

• Closed as program error.

Error description

• WebSphere Application Server v7.0.0.13 EJBDeploy fails if the
  input EAR includes mulitple EJB JAR files that have the same
  name but are in different root folders.
  
  Note: Rational Application Developer v7.5.5.y provides EJBDeploy
  for WebSphere Application Server v7.0.0.x.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Importing an EAR that contains multiple modules of the same
  type with the same name in different directories would
  result in a name collision for the projects that would be
  created for those modules.  This collision can be averted by
  renaming the projects in the UI import wizard; However, with
  non-UI tools, such as EJB Deploy, this is not possible.
  
  An example using the EJB Deploy tool:
  
  EJB Deploy configuration directory:
  d:\IBM\WebSphere\AppServer\7.0\deploytool\itp\configuration/
  
  framework search path:
  d:\IBM\WebSphere\AppServer\7.0\deploytool\itp\plugins
  build: RAD755-I20091202_2257
  
  Creating the project.
  
  org.eclipse.core.commands.ExecutionException: Colliding
  project name "
  HelloEjb3Example_EJB " between archives "
  michael/HelloEjb3Example.jar "
  and " yulimin/HelloEjb3Example.jar ".
  
  at
  com.ibm.etools.ejbdeploy.batch.plugin.BatchExtension.importE
  ar(BatchExtension.java:1116)
  

Problem conclusion

• If an EAR contains multiple modules of the same type with
  the same name in different directories, a numeric suffix is
  now added to the proposed name, thus generating a
  non-colliding default name proposal.
  
  The fix for this is included in Rational Application
  Developer v7.5.5.4.
  

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

• R755 PSN

     UP