[ http://issues.apache.org/jira/browse/AXIS-1887?page=comments#action_61169 ] Davanum Srinivas commented on AXIS-1887: ----------------------------------------
Can you please suggest a patch? thanks, dims > tcpmon unable to display messages: faulty lookup of encoding > ------------------------------------------------------------ > > Key: AXIS-1887 > URL: http://issues.apache.org/jira/browse/AXIS-1887 > Project: Axis > Type: Bug > Versions: 1.2RC3 > Environment: ALL (particularly tcpmon running independent of axis > server/client) > Reporter: Clive Brettingham-Moore > Priority: Minor > > The handling of encoding introduced to fix AXIS-1815, ie using > XMLUtils.getEncoding() is fragile and greatly increases the classpath needed > to run tcpmon (use of XMLUtils forces loading of saaj, jaxrpc, > commons-logging and commons-discovery; previously only axis.jar was > required), and the value returned appears to have no significance to the > message being displayed anyway (AFAICS if tcpmon is in a separate vm it will > just default since there will be no engine and no messages) > Encoding would be better picked up from the content-type header and/or the > xml declaration of the message, or let the user manually specify a fallback > encoding for display. > If you run tcpmon with only axis.jar and don't look at the console (assuming > you even run it from one) it only displays the headers for the request and > nothing else (due to class not found error), which could be very confusing > for people trying to debug an app. This bug will catch many who run tcpmon > from the command line or scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
