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 On Tue, 20 Jan 2004, Scott M Stark wrote: > What are the other 3 known compliance issues? 3.2 and head should be in > synch > on class loaders and I need to merge some of the changes made to the jmx > layer so I want to get these test working before doing the merge. > > > 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 10:49 AM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] jmx unit tests > > > the jmx module unit tests are the ones we run against, the ones in > testsuite were never maintained. > > At least 3 of the 4 failures on compliance are known issues (and > reported as such), I don't know about the JMX 1.2 notification emitter > one. > > The two errors are both related to classloading, at least at some point > the loader repository impl. in 3.2 worked correctly with these, whatever > the diffs in classloading were were not ported back to head. > > The error in head implementation tests is new, and looks like is related > to classloading again. The failure is a known issue and reported as > such. > > I haven't run the serialization tests, Adrian will know about those. > > I haven't run these against 3.2 for a long while, the number of failures > seems high. > > Serialization-1.0 full failure seems to indicate it's not running > against JMX 1.0 > > -- 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 > > ------------------------------------------------------- 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
