[jboss-jira] [JBoss JIRA] Commented: (JBAS-2037) Bug in the JBoss HTML adaptor.

Bug in the JBoss HTML adaptor. ------------------------------ Key: JBAS-2037 URL: https://jira.jboss.org/jira/browse/JBAS-2037 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-3.2.5 Final, JBossAS-4.0.0 Final, JBossAS-4.0.1RC1, JBossAS-3.2.6 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1, JBossAS-4.0.2 Final, JBossAS-4.0.3RC1 Reporter: jean deruelle Assignee: Amit Bhayani "The set of characters in a value is also limited. If special characters may occur, it is recommended that the value be quoted, using ObjectName.quote. If the value for a given key is sometimes quoted, then it should always be quoted. By default, if a value is a string (rather than a number, say), then it should be quoted unless you are sure that it will never contain special characters." quoted from java management best practices (see http://java.sun.com/products/JavaManagement/best-practices.html#mozTocId6... in section ObjectNameSyntax) When a JMX value is quoted, it causes problems to invoke methods through thr Jboss jmx web console : So my feeling is that the problem comes from the jboss jmx console jsp pages. The thing is that the quotes in the jmx object name are not encoded to the html format in the jsp pages and so the first opening quote is interpreted as the final quote of the html field. Here is a quick fix for Jboss-3.2.6 : Add the following lines to %JBOSS_HOME%\server\all\deploy\jmx-console.war\inspectMBean.jsp after line 141 <%objectNameString=objectNameString.replaceAll("\"","&quot;"); //objectNameString=URLEncoder.encode(objectNameString);%> It was a quick fix to fit my needs but the line should really be the one commented but in that case the HtmlAdaptorServlet from Jboss cannot handle it correctly because it doesn't do a URLDecoder.decode of the objectNameString stored in the request parameter called "name". But I might be wrong here in saying that it comes from jboss, maybe I missed something along the way. Can someone confirm this bug or help me out there ? Thx Best regards Jean