It appears the the create<Method> patch has broken create for CMP 2 entities. Now create always returns null. Was the testsuite run before this patch was committed?
I'll see if I can fix it. -dain Dain Sundstrom wrote: > I'm looking into it. > > -dain > > Scott M Stark wrote: > >> All of the new errors are in the org.jboss.test.cmp2.relationship >> package, >> and all are NPEs in the unit test code. One example stack trace is: >> >> N/A >> >> java.lang.NullPointerException >> at >> org.jboss.test.cmp2.relationship.oneToOneBidirectional.ABTest.beforeChange(A >> >> BTest.java:85) >> at >> org.jboss.test.cmp2.relationship.oneToOneBidirectional.ABTest.test_a1SetB_a2 >> >> GetB_Table(ABTest.java:97) >> at java.lang.reflect.Method.invoke(Native Method) >> at junit.framework.TestCase.runTest(TestCase.java:166) >> at junit.framework.TestCase.runBare(TestCase.java:140) >> at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133) >> at >> net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.jav >> >> a:102) >> at >> net.sourceforge.junitejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:44) >> at java.lang.reflect.Method.invoke(Native Method) >> at >> org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(Stateles >> >> sSessionContainer.java:642) >> at >> org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor >> >> .java:96) >> at >> org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxIntercep >> >> torBMT.java:144) >> at >> org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62) >> at >> org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSe >> >> ssionInstanceInterceptor.java:77) >> at >> org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:12 >> >> 7) >> at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) >> at >> org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.jav >> >> a:308) >> at org.jboss.ejb.Container.invoke(Container.java:668) >> at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555) >> at >> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) >> at >> org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:363) >> at java.lang.reflect.Method.invoke(Native Method) >> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) >> at sun.rmi.transport.Transport$1.run(Transport.java:152) >> at java.security.AccessController.doPrivileged(Native Method) >> at sun.rmi.transport.Transport.serviceCall(Transport.java:148) >> at >> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465) >> at >> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:7 >> >> 06) >> at java.lang.Thread.run(Thread.java:484) >> >> xxxxxxxxxxxxxxxxxxxxxxxx >> Scott Stark >> Chief Technology Officer >> JBoss Group, LLC >> xxxxxxxxxxxxxxxxxxxxxxxx >> ----- Original Message ----- >> From: "marc fleury" <[EMAIL PROTECTED]> >> To: "Jboss-Development@Lists. Sourceforge. Net" >> <[EMAIL PROTECTED]> >> Sent: Tuesday, March 05, 2002 8:55 PM >> Subject: [JBoss-dev] Tests something broke >> >> >> >>> Adrian or David, >>> >>> ok I know I am on shaky grounds to raise a flag (heck I broke the build >>> >> for >> >>> a week) but it seems that one of your builds just broke the tests and we >>> have 20 more testst that fail since yesterday. >>> >>> Can you guys double check with the testsuite? >>> >>> marcf >>> >>> >> >> >> >> _______________________________________________ >> Jboss-development mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/jboss-development >> > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
