PI34529: NULLPOINTEREXCEPTIONS OCCUR WHEN ADDING EGLAR FILES TO THE EGL BUILD PATH INDICATING THEY ARE CORRUPT

Rational Business Developer 9.5.0.1
Rational Business Developer Fix Pack 1 (9.1.1.1) for 9.1.1
Rational Business Developer 9.5.1

APAR status

• Closed as program error.

Error description

• when adding EGLAR files to the EGL build path of a project they
  produce an EDT error in problems view and associated errors are
  shown in the .log eg:
  Problems occurred when invoking code from plug-in:
  "org.eclipse.ui.navigator".
  !STACK 0
  java.lang.NullPointerException
      at
  com.ibm.etools.egl.model.internal.core.EglarPackageFragmentRoot.
  computeChildren(Unknown Source)
  ...........
  MESSAGE An exception occurred invoking extension:
  org.eclipse.ui.navigator.resourceContent for object P/Test
  !STACK 0
  java.lang.NullPointerException
      at
  com.ibm.etools.egl.model.internal.core.EglarPackageFragmentRoot.
  computeChildren(Unknown Source)
  .............
  !MESSAGE EDT Build Failure
  !STACK 0
  com.ibm.etools.edt.internal.core.builder.BuildException:
  java.util.zip.ZipException: error in opening zip file
      at
  com.ibm.etools.edt.common.internal.io.ZipFileBuildPathEntry.proc
  essEntries(Unknown Source)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users attempting to use an eglar file that has been          *
  * corrupted.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * A nullpointer exception can occur when trying to use an      *
  * eglar file that is corrupt. This can result in numerous      *
  * red-X's in the workspace environment.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The logic has been modified to handle the nullpointer and
  instead of giving an exception, the eglar file will be handled
  as if it has no entries in it. It cannot fix the corrupted file.
  The user will need to determine the cause of the corruption.
  

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 BUS DEV

• Fixed component ID

  5724S5000

Applicable component levels

• R911 PSY

     UP

• R950 PSY

     UP