-
1. Re: Session Bean / Classpath trobules
bdecoste Apr 6, 2006 3:06 PM (in response to faelin)Try deploying the .war and .jar in an .ear - you should have no problems.
-
2. Re: Session Bean / Classpath trobules
bdecoste Apr 6, 2006 3:47 PM (in response to faelin)Your Bar class is not Serializable. It needs to be.
-
3. Re: Session Bean / Classpath trobules
faelin Apr 9, 2006 1:40 PM (in response to faelin)Actually, all classes need to be loaded in the same classloader, as I found. The .war's were loaded by the WebappClassLoader, while all other by the JBoss' unified class loader. I solved the problem by making the .war's use the same classloader (which has some disadvantages, but should work for me). Apart from that, I do not want to deploy in the same .ear, if that is possible...
-
4. Re: Session Bean / Classpath trobules
marcwimmer Apr 10, 2006 1:41 AM (in response to faelin)I had troubles with that, too...
have a look at this post perhaps:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935886#3935886 -
5. Re: Session Bean / Classpath trobules
faelin Apr 10, 2006 2:45 AM (in response to faelin)Hm, unfortunatelly it won't help me. I am passing a plain java bean as a parameter to a session bean, because the arguments I had to pass are too much. I keep it in the same .jar file with the session beans (because that seems reasonable to me).
But thanks for you link - that will be of big assistance, since I will face that problem myself. Maybe I should try putting them in one .ear, after all.