Okay: I've tried setting up JBoss to allow hot redeployment of EJBs without clobbering any running servlets. I get a ClassCastException on calls after redeploy. This doesn't happen if Jetty is run in a separate JVM -- which I'm told is due to serialization, where the EJB stub is 'recreated' on the client side, rather than passed as a reference.
This is problematic for me but not insurmountable, as I can always run Jetty in its own process if I have to. However, I've just written another test where an EJB calls another EJB, which fails in the same way. This is far more serious. We need to be able to hot-deploy components without interrupting service to clients; and while that could be resolved for servlets as above, it's not practical to run a separate JBoss server for every component of our system. I'd got the impression that ByValueInvokerInterceptor was the appropriate tool to force serialization on local calls, but it doesn't seem to change anything: .. at org.jboss.invocation.ByValueInvokerInterceptor.invoke(ByValueInvokerInterceptor.java:65) .. Given that it can be made to work across separate JVMs, it *must* be possible to do this in one JVM somehow. It's really important that I solve this soon; can someone please help me out? Andrew ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
