The 3.2 branch is down to the same failures as head. The issue with the
two class loader failures is due to the fact that we don't like anything
but UCLs in the ULR and the MLet is transferred into an equivalent UCL
on
addition, but we lose the mapping between the UCL and MLet and when the
MLet is removed we can't find the associated UCL in the ULR. This should
be easy to fix by adding a non-UCL to UCL map to the ULR.
[java] 3)
testMLetLoadClassFromURLInConstructor(test.compliance.loading.MLetTEST)
junit.framework.AssertionFailedError: class
test.compliance.loading.support.Trivial was still found in CL
repository.
[java] at
test.compliance.loading.MLetTEST.testMLetLoadClassFromURLInConstructor(M
LetTEST.java:102)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[java] at
test.compliance.ComplianceSUITE.main(ComplianceSUITE.java:48)
[java] 4) testBasicMLetFileLoad(test.compliance.loading.MLetTEST)
junit.framework.AssertionFailedError: class
test.compliance.loading.support.Trivial was already found in CL
repository.
[java] at
test.compliance.loading.MLetTEST.testBasicMLetFileLoad(MLetTEST.java:122
)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
[java] at
test.compliance.ComplianceSUITE.main(ComplianceSUITE.java:48)
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Juha
Lindfors
Sent: Tuesday, January 20, 2004 2:28 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] jmx unit tests
JBOSS-HEAD:
/cygdrive/d/jboss-head/jmx
$ sh build.sh test-compliance-JBossMX
Searching for build.xml ...
Buildfile: d:\jboss-head\jmx\build.xml
...
[java] 1) testNotificationEmitterRemoveTripletFailsOnBroadcaster
(test.compliance.server.MBeanServerInvocationHandlerTestCase)
junit.framework.AssertionFailedError: removeNotificationListener
(NotificationListener, NotificationFilter, Object)should not work for a
broadcaster
* This is JMX1.2 API, so Adrian will know the details
[java] 2)
testGetDescriptor(test.compliance.modelmbean.ModelMBeanInfoSupportTEST)
junit.framework.AssertionFailedError: FAILS IN JBOSSMX:
We incorrectly return descriptor type 'constructor' here -- should be
'operation'
* Incorrect metadata value for a model mbean constructor, I vaguely
remember 1.2 spec has a different semantic specified here compared to
1.0
[java] 4) testPathological(test.compliance.query.QueryTestCase)
junit.framework.AssertionFailedError: FAILS IN JBossMX: expected
Hello(?:.) to match Hello(?:.)
* IIRC, spec ambiguity, Adrian might remember more on this.
I don't think any of the above needs fixing to port changes to jmx
layer.
The two errors on classloading and one error on classloading in
implementation suite however might be worth looking at.
-- Juha
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
