[JBoss-dev] jboss-3.2-testsuite build.74 Build Successful

[qa]

View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-3.2-testsuite?log=log20050217124043Lbuild.74

BUILD COMPLETE -  build.74

Date of build: 02/17/2005 12:40:43

Time to build: 94 minutes 7 seconds

Last changed: 02/16/2005 19:39:07

Last log entry: [JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.

Unit Tests: (1936)  Total Errors and Failures: (27)

testNoClassDefFoundError org.jboss.test.classloader.test.BasicLoaderUnitTestCase testSessionHandleNoDefaultJNDI org.jboss.test.cts.test.StatefulSessionUnitTestCase testBMTSessionHandleNoDefaultJNDI org.jboss.test.cts.test.StatefulSessionUnitTestCase unknown org.jboss.test.jbossmq.test.LargeMessageUnitTestCase unknown org.jboss.test.jbossmq.test.OILConnectionUnitTestCase testQueueMessageOrder org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testRequestReplyQueue org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTemporaryQueueDelete org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTemporaryTopicDelete org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationQueueSend org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationQueueBrowse org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testInvalidDestinationTopicPublish org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testErrorsTopicSubscribe org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testCreateQueue org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testMessageListener org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testApplicationServerStuff org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopics org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicNoLocal org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicNoLocalBounce org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicSelectorChange org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testTopicSelectorNullOrEmpty org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSendReceiveOutdated org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSendReceiveExpired org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSendListenOutdated org.jboss.test.jbossmq.test.OILJBossMQUnitTestCase testSessionHandleNoDefaultJNDI org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase testBMTSessionHandleNoDefaultJNDI org.jboss.test.securitymgr.test.StatefulSessionUnitTestCase testSRPLoginWithAuxChallenge org.jboss.test.security.test.SRPLoginModuleUnitTestCase

Modifications since last build:  (5)
1.9.2.8	modified	ejort	server/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.java	[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.
1.5.2.4	modified	ejort	server/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.java	[JBAS-1479] Use JNDI for SFSB handleAllow a system property to be used for backwards compatiblity of handle state:org.jboss.ejb.sfsb.handle.V327This will allow handles created from the new code to be used with older clients.
1.9.2.7	modified	ejort	server/src/main/org/jboss/proxy/ejb/handle/StatefulHandleImpl.java	Switch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).
1.5.2.3	modified	ejort	server/src/main/org/jboss/proxy/ejb/StatefulSessionInterceptor.java	Switch over the SFSB handle to use the jndi strategy of the other handles.This is backwards compatible in the sense that the new code will work with older handles(as long as the default initial context produces the correct jndi handle to lookup the home).However, older clients won't be able to use the new handle because they tried to use theinvoker which is no longer present in the handle.Using the invoker was incorrect. Depending on the transport, it did not survive serverrestarts (which is the whole point of using a handle rather than an EJBObject).
1.5.4.7	modified	ejort	security/src/main/org/jboss/security/srp/SRPRemoteServer.java	This exception can no longer occur