PK93967: WCM API ITERATOR'S CAN RETURN NULL

APAR status

• Closed as program error.

Error description

• Within the WCM API, some of the iterators can return null
  instead of a NoSuchElementException when the end of the iterator
  is reached. Note: This defect does not effect the
  iterator.hasNext() method which should always be called to
  determine if the next element is available.
  
  Effected WCM API methods include:
  Workspace.contentSearch
  Workspace.findByName
  Workspace.findContentByAuthoringTemplate
  Workspace.findContentByWorkflowStage
  Workspace.findContentModifiedBetween
  Workspace.findContentModifiedSince
  Workspace.findDocumentsByWorkflowStage
  Workspace.findDocumentsModifiedBetween
  Workspace.findDocumentsModifiedSince
  Site.getAllChildren
  Site.getAllDirectChildren
  Site.getDirectChildren
  SiteArea.getAllChildren
  SiteArea.getAllDirectChildren
  SiteArea.getDirectChildren
  

Local fix

• This defect is unnoticeable if the standard JAVA convention of
  using iterator.hasNext() is used, as the hasNext() method does
  return 'false' when no further elements are available.
  

Problem summary

• WCM's multiple iterator which is used to group the results of
  multiple queries together (such as for draft and
  published/expired queries), wasn't checking if the returned
  element was going to be null and thus throwing a
  NoSuchElementException instead.
  

Problem conclusion

• Within the WCM Multiple iterator, we now check whether the
  returned element is now and thus throw a NoSuchElementException
  instead.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R60J PSY

     UP