Thanks again, I got it working now from svn (still need to update the openejb-tmp downloads).
One more thing, the 21 errors that occur from running the tests twice, is it really a "unknown reason"? Seems like a hsqldb driver message due to still having some lock on previously closed sessions. -Dario > On Sep 21, 2007, at 1:35 AM, Dario Laverde wrote: > >> Thanks Dain, >> >>> I added the @Local annotation to the AnnotatedEJBLocal interface and >>> added a @Remote AnnotatedEJBRemote interface to the example; both >>> work fine for me. >>> >>> Can you try the servlet-examples war? >> >> You don't have the remote interface in your examples, > > If you check the servlet-samples, you will see I added an annotated > remote interface to the code. > > http://svn.apache.org/viewvc/openejb/trunk/openejb3/examples/servlet- > samples/src/main/java/org/apache/openejb/examples/servlet/ > > >> but adding one still gives me >> the following when getting the datasource: >> >> java.io.NotSerializableException: >> org.apache.openejb.resource.jdbc.BasicManagedDataSource >> java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) >> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java: >> 302) org.apache.openejb.core.ivm.BaseEjbProxyHandler.copyObj >> (BaseEjbProxyHandler.java:503) >> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke >> (BaseEjbProxyHandler.java:259) >> org.apache.openejb.util.proxy.Jdk13InvocationHandler.invoke >> (Jdk13InvocationHandler.java:49) >> $Proxy42.getDs(Unknown >> Source) org.apache.openejb.examples.servlet.AnnotatedServlet.doGet >> (AnnotatedServlet.java:44) > > Based on the stacktrace it appears that your remote interface > includes the "DataSource getDs();" method. When you call this > method, you get a NotSerializableException because a DataSource > object is not serializable. The EJB specification restricts remote > interface to only use serializable data types. > > If you remove this method, I bet your code will work. > >>> As for the test client jar, I rewrote the packing configuration for >>> it the other day, and tested it on linux and windows. So, if it was >>> broken before, I'm confident it is fixed now :) >> >> It's fixed in your war file but still broken in the current snapshot. >> >> I also noticed that I can't "undeploy" the beans by reloading the >> web application >> (or both the web app and openejb for that matter). Is it possible >> to avoid >> restarting Tomcat every time one just wants to reload the web app? > > Yes it is possible... I just need to code up the stop listener :) > I'll try to implement that today. > > -dain >
