axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Clayton (JIRA)" <>
Subject [jira] Commented: (AXIS-2350) array index oob bug in StringUtils.unescapeNumericChar()
Date Wed, 21 Dec 2005 19:30:30 GMT
    [ ] 

Tony Clayton commented on AXIS-2350:

I should mention that this bug manifests itself in the tcpmon utility in an ugly way; an exception
is thrown and ignored internally, and all processing and proxying of the current message stops.
 So, any remaining text just "disappears".

A workaround for tcpmon is to ensure that the "Numeric" checkbox is checked, in which case
the unescapeNumericChar() method is not used and the numeric encodings are printed to the
tcpmon window verbatim.

> array index oob bug in StringUtils.unescapeNumericChar()
> --------------------------------------------------------
>          Key: AXIS-2350
>          URL:
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.3
>  Environment: XP Pro, JDK1.4.2, axis 1.3
>     Reporter: Tony Clayton
>     Priority: Minor
>  Attachments: axis-1_3.StringUtils.patch, axis-1_3.TestStringUtils.patch
> I seem to have uncovered a bug in the org.apache.axis.utils.StringUtils class.
> The unescapeNumericChar() method is throwing a StringIndexOutOfBoundsException for the
following input string:
>   String str = "Terse numeric encoding breaks axis 1.3: &#xA;aa";
> The code expects only numeric character encodings in a four-digit format, ie: &#x000A;
and behaves badly otherwise.
> In this particular case, the gSOAP C++ library is sending back the terse format (&#xA;)
from the SOAP server.
> I have implemented an updated unescapeNumericChar() method to fix this problem. I also
write a junit test case.
> I'll attach both.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message