Re: Bug in JDOM char verification

[Jason Hunter]

There's a post by Elliotte Rusty Harold (who wrote the verifier) to 
jdom-interest about this issue.  I'm leaving for a plane in literally 
two minutes, so I can't research it.  But the archives are searchable at 
servlets.com/archive.

-jh-

Stefano Mazzocchi wrote:

look at this code:

    public static String checkCharacterData(String text) {
        if (text == null) {
            return "A null is not a legal XML value";
        }
        // do check
        for (int i = 0, len = text.length(); i<len; i++) {
            if (!isXMLCharacter(text.charAt(i))) {
                // Likely this character can't be easily displayed
                // because it's a control so we use it'd hexadecimal
                // representation in the reason.
                return ("0x" + Integer.toHexString(text.charAt(i))
                 + " is not a legal XML character");
            }
        }
        // If we got here, everything is OK
        return null;
    }
there is a big issue here: what about high-unicode characters like 
&0x10000; and above?

Slide fails to pass one of the litmus webdav compliance tests because of 
this.

Any suggestion on how to patch it? anyone?

--
Stefano.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]