PK59600: Dynamic recomputing of the RAD v7 WTP EAR

APAR status

• Closed as user error.

Error description

• Dynamic recomputing of the RAD v7 WTP  EAR
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• The customer is starting with a v6 RAD project and importing
  it into RAD v7.  Back in v6 RAD relied on individual
  .classpath entries for every single project dependency to
  resolve the build path.
  For example, if a WAR project depended on a Java Utility
  project in the MANIFEST.MF then there would be a .classpath
  entry to that Java Utility project.  In v7, however, this is
  not the case.  V7 relies on the the EAR Libraries classpath
  container which resolves all projects by reading the
  MANIFEST.MF and the workspace meta-data.  Though v7 has
  moved away from modifying the .classpath directly the old
  .classpath entries are still supported, but they are
  discouraged.  There is a classpath checker (under
  Preferences -? J2EE) which can detect when there is a
  .classpath entry in place where it is not needed (because it
  can be dynamically computed from the MANIFEST.MF) which by
  default adds a warning message to the Errors view.
  We will not perform this cleanup automatically, though it is
  close to automatic with the quickfix available on the
  warning message (you can clean them all in one go by
  selecting the find similar problems button).  The reason we
  can't make this fully automatic is there may be scenarios
  where customers need to have control over their .classpath.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels