PI52294: UNNECESSARY EXCEPTIONS AND MESSAGES GENERATED IN SYSTEMOUT LOG W HEN HTML IS SET WITH INVALID CHARACTERS VIA WCM API

APAR status

• Closed as program error.

Error description

• When setting a html element with text that contains invalid
  characters using the WCM Java API, lots of unnecessary
  exceptions and messages are generated into the SystemOut log
  file. The following exceptions can be seen whenever this
  occurs:
  
  Example #1:
  Caused by: com.aptrix.pluto.cmpnt.codec.SXMLException: At line
  5: Invalid character (0) found. Only characters allowed in XML
  are supported<br>At line 13 : Invalid character (0) found. Only
  characters allowed in XML are supported<br>At line 14 : Invalid
  character (0) found. Only characters allowed in XML are
  supported<br>At line 14 : Invalid character (0) found. Only
  characters allowed in XML are supported
  at com.aptrix.pluto.cmpnt.codec.SXMLParser.parse(SXMLParser
  .java:597)
  at com.aptrix.pluto.cmpnt.codec.SXMLParser.parse(SXMLParser
  .java:107)
  at com.aptrix.pluto.cmpnt.codec.SXMLCodec.toCmpnt(SXMLCodec
  .java:453)
  at com.aptrix.pluto.cmpnt.codec.SXMLCodec.toCmpnt(SXMLCodec
  .java:433)
  at com.ibm.workplace.wcm.api.WCM_ArrayComponentDelegate
  .setHTML_aroundBody2(WCM_ArrayComponentDelegate.java:130)
  ...
  
  Example #2:
  SXMLErrors W SXMLErrors: At line 5 : Invalid character (0)
  found. Only characters allowed in XML are supported
  SXMLErrors W SXMLErrors: is m_cause == nullfalse
  SXMLErrors W SXMLErrors: is m_cause == nulltrue
  .....
  

Local fix

• No functional impact. This is a logging issue only and the
  messages in the logs can safely be ignored.
  

Problem summary

• When setting a html element with text that contains invalid
  characters using the WCM Java API, lots of unnecessary
  exceptions and messages are generated into the SystemOut log
  file. The following exceptions can be seen whenever this occurs:
  
  Example #1:
  Caused by: com.aptrix.pluto.cmpnt.codec.SXMLException: At line
  5: Invalid character (0) found. Only characters allowed in XML
  are supported<br>At line 13 : Invalid character (0) found. Only
  characters allowed in XML are supported<br>At line 14 : Invalid
  character (0) found. Only characters allowed in XML are
  supported<br>At line 14 : Invalid character (0) found. Only
  characters allowed in XML are supported
  at com.aptrix.pluto.cmpnt.codec.SXMLParser.parse(SXMLParser
  .java:597)
  at com.aptrix.pluto.cmpnt.codec.SXMLParser.parse(SXMLParser
  .java:107)
  at com.aptrix.pluto.cmpnt.codec.SXMLCodec.toCmpnt(SXMLCodec
  .java:453)
  at com.aptrix.pluto.cmpnt.codec.SXMLCodec.toCmpnt(SXMLCodec
  .java:433)
  at com.ibm.workplace.wcm.api.WCM_ArrayComponentDelegate
  .setHTML_aroundBody2(WCM_ArrayComponentDelegate.java:130)
  ...
  
  Example #2:
  SXMLErrors W SXMLErrors: At line 5 : Invalid character (0)
  found. Only characters allowed in XML are supported
  SXMLErrors W SXMLErrors: is m_cause == nullfalse
  SXMLErrors W SXMLErrors: is m_cause == nulltrue
  .....
  

Problem conclusion

• The error handling for the above error case has been improved to
  prevent unnecessary messages from being printed to the logs.
  
  As this is a valid exception, a ParseException will now instead
  be thrown. Any custom code which uses the public API should
  handle this exception appropriately. Refer to the following for
  further details regarding the exception:
  com.ibm.workplace.wcm.api.exceptions.ParseException
  

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

• R850 PSY

     UP