This content has been marked as final.
Show 4 replies
-
1. Re: Testsuite failures for MalformedTestCase testMalformed t
ryan.campbell Aug 23, 2006 12:46 PM (in response to mwringe)Perhaps we should just ignore this if running under jdk5?
-
2. Re: Testsuite failures for MalformedTestCase testMalformed t
starksm64 Aug 23, 2006 3:26 PM (in response to mwringe)-Could you please explain this issue a little bit more?
A jmx object name string of "domain:=,foo=bar" violates the jmx spec ObjectName syntax of:
[domainName]:property=value[,property=value]*
and ObjectName javadoc which states that
http://java.sun.com/j2se/1.5.0/docs/api/index.html
The key properties are an unordered set of keys and associated values.
Each key is a nonempty string of characters which may not contain any of the characters comma (,), equals (=), colon, asterisk, or question mark. The same key may not occur twice in a given ObjectName.
Each value associated with a key is a string of characters that is either unquoted or quoted.
An unquoted value is a possibly empty string of characters which may not contain any of the characters comma, equals, colon, quote, asterisk, or question mark.
I have submitted a bug report to sun on this.
-Why does JBoss have separate versions of Sun's classes?
We have had our own implementation of JMX since it was an extension package to jdk1.3.
-This test usually passes on the 1.4.2 JVM, is this test only meant to be run on a 1.4.2 JVM?
This test is only meaningful for jdk < 5 to test our implementation. -
3. Re: Testsuite failures for MalformedTestCase testMalformed t
mwringe Aug 23, 2006 5:00 PM (in response to mwringe)Since this test is only meaningful is the JVM version is less than 1.5, shouldn't this test be disabled if a 1.5 jvm is present?
-
4. Re: Testsuite failures for MalformedTestCase testMalformed t
starksm64 Aug 23, 2006 10:04 PM (in response to mwringe)It would be better categorized as a known failure that can be ignored.