Topic:   ServerError: (com.wm.app.b2b.server.ServiceException: [ISC.0042.9332] Malformed entity reference: &023721
Feb 21, 2012 21:32 2 Replies 6008 Views Pia
Prev Next
Topic Replies (2)
  1. 1
    idnkx user

    Pia

    Hi experts,

    We are getting this error while running a Integration with a application, when we are turning the integration off we are not getting any errors on our server.

    Error:

    ServerError: (com.wm.app.b2b.server.ServiceException: [ISC.0042.9332] Malformed entity reference: &023721

    Could anyone kindly analyze this issue and let me know the root cause or corrective actions.

    Thanks,
    Pia

    1
    idnkx user

    Vikram

    Hi Pia,


    The Root cause for this issue may be an XML document with an [b]unencoded '&'[/b] or any [b]special character [/b]in the data is not valid XML, we should be receiving encoded XML.

    Integration Server does not detect malformed entities during XML parsing.

    This error occurs because the XML parser does not detect malformed entities and parses them into an empty string. For example, "> ;" becomes "".

    According to the XML 1.0 spec, an entity or character spec is of the form &string; with no white space. For example, > is a legal reference and > ; is illegal.

    By default the Integration Server throws an exception if it detects a malformed entity. Specifically the pub.xml:xmlNodeToDocument service will throw the following error:

    com.wm.app.b2b.server.ServiceException:
    [ISC.0042.9332] Malformed entity reference:

    Corrective actions:


    1) This should be corrected at the source. Request your partner/Legacy to send HTML encoded for spl chars in the xmldata field. values ..

    to name some:

    & to &
    < to <
    > >

    2) For customers who prefer to allow the malformed entries, the following configuration property has to be added.

    watt.server.xml.enforceEntityRef=false

    Set this property to "false" to prevent the Integration Server from throwing an exception when the XML parser detects a malformed entity.



    3) Use a substitute for our special character which webMethods does not refer to as a special character while we are sending the data.



    Since the malformed exception/error normally happens if the XML document contains special character, in this case '&' (this is also true in Java handling of XML document).

    Below might give you an idea for handling this at the code:

    i: You may want to include a call to stringToDocument or documentToXMLString (encode=true) with encoding = true to encode all '&'.


    ii: Or Write a java service to replace the '&' with 'amp' and other related XML special characters.


    Hope this helps


    Regards,
    Vikram

Leave a Reply
Guest User

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.


Let`s Connect