IBM Support

JR47331: ILLEGAL CHARACTER EXCEPTION OCCURS WHEN RUNNING TW.SYSTEM.USER.ATTRIBUTES.TOXML

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When executing tw.system.user.attributes.toXML() or
    toXMLString(), Illegal Character exception occurs.
    Internal Script error occurs: org.jdom.IllegalNameException:
    The name \"Task Email Address\" is not legal for JDOM/XML
    elements: XML names cannot contain the character \" \"."
    [8/7/15 11:24:42:487 EDT] 0000012b wle           E
    CWLLG2015E:  An
    unexpected runtime exception occurred. See exception for more
    details.
    Error: Export failed on UCA 'StartPeriodicDistUCA': The data
    "StartPeriodicDistUCA" is not legal for a JDOM attribute: 0x1f
    is not a legal XML character..
                                     com.ibm.bpm.pal.PALException:
    Export failed on UCA 'StartPeriodicDistUCA': The data
    "StartPeriodicDistUCA" is not legal for a JDOM attribute: 0x1f
    is not a legal XML character.
       at com.ibm.bpm.pal.action.BaseActionsImpl.executeAction
    (BaseActionsImpl.java:330)
       at com.ibm.bpm.pal.action.SnapshotActionsImpl.exportSnapshot
    (SnapshotActionsImpl.java:203)
    .
    ...
    Caused by: com.lombardisoftware.client.delegate.
    BusinessDelegateException: Export failed on UCA
    'StartPeriodicDistUCA': The data "StartPeriodicDistUCA"
    is not legal for a JDOM attribute: 0x1f is not a legal XML
    character.
       at
    com.lombardisoftware.client.delegate.BusinessDelegateException.
    asBusinessDelegateException(BusinessDelegateException.java:41)
       at com.lombardisoftware.client.delegate.
    ExportImportServiceDelegateDefault.exportWithDependencies
    (ExportImportServiceDelegateDefault.java:292)
    at com.lombardisoftware.server.ejb.repositoryservices.
    RepositoryServicesCore.exportWithDependenciesInternal
    (RepositoryServicesCore.java:827)
    This happens for even the default custom user
    attributes. This only happens for Record type objects as we
    are not handling the illegal characters properly when
    serializing.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications using                          *
    *                  tw.system.user.attributes.toXML()/toXMLStri *
    *                  n                                           *
    *                  g() to obtain user attribute information.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: An IllegalNameException occurs when     *
    *                      the property name appear to have valid  *
    *                      XML characters.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When executing tw.system.user.attributes.toXML() or
    toXMLString() to obtain default user attributes properties, an
    IllegalNameException occurs.
    A similar exception stack can be seen:
    Caused by: org.jdom.IllegalNameException: The name "Portal
    Default Page" is not legal for JDOM/XML elements: XML names
    cannot contain the character " ".
    at org.jdom.Element.setName(Element.java:207)
    at org.jdom.Element.<init>(Element.java:141)
    at org.jdom.Element.<init>(Element.java:153)
    at
    com.lombardisoftware.core.VariableObjectSerializer.serializeReco
    rd(VariableObjectSerializer.java:648)
    at
    com.lombardisoftware.core.VariableObjectSerializer.serializeSyst
    emType(VariableObjectSerializer.java:585)
    at
    com.lombardisoftware.core.VariableObjectSerializer.serializeInte
    rnal(VariableObjectSerializer.java:291)
    

Problem conclusion

  • Code changes have been made to handle the IllegalNameException
    and properly set the attribute name.  An interim fix is
    available on v8.0.1.1.  The fix will be integrated into the
    next fix pack.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47331

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-07-26

  • Closed date

    2013-09-09

  • Last modified date

    2017-05-09

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
07 January 2022