JR44477: SERVICEDEPLOY UNABLE TO CREATE EAR WHEN MORE THEN ONE MANIFEST.M F GENERATED FOR PROJECT

APAR status

• Closed as program error.

Error description

• Customer may meet following error when they are using
  servicedeploy
  
  [exec] Severity:  [error]
  [exec] Description:  Only a type can be imported. [class]
  resolves
  to a package
  [exec] Resource:  [class_name].java
  [exec] Location:      10
  [exec]
  [exec] Severity:  [error]
  [exec] Description:  [object] cannot be resolved to a type
  [exec] Resource:  [class_name].java
  [exec] Location:      71
  [exec]
  
  And java.io.FileNotFoundException can be found if the trace for
  servicedeploy enabled.
  This APAR will fix this issue.
  

Local fix

• Removing the entry
  "psam_process_service/src/META-INF/MANIFEST.MF" from
  the project interchange file will work around this issue:
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Websphere process server 7.0 users          *
  ****************************************************************
  * PROBLEM DESCRIPTION: When customer using service deploy.     *
  *                      The FileNotFound exception may          *
  *                      happen when there are more then one     *
  *                      MainFest.mf file                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  For sometime the project may contains more then one
  mainfest.mf file. It's as designed but may bring some issue to
  the servicedeploy step. Some class may not been found for the
  deploy process because one of the mainfest.mf file may be
  ignored. This issue can be fixed by this ifix.
  

Problem conclusion

• The fix will consider the extra mainfest.mf file and process
  that correctly to generate the correct EAR file.
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  
  The ifix file is available on the fixcentral.
  

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

  WEB PROC SERVER

• Fixed component ID

  5724L0100

Applicable component levels

• R700 PSY

     UP