Session Bean / Classpath trobules

[faelin]

Hi.

I'm experiencing classloading problems when using the session beans in EJB 3.0. Basically, I want to pass my own objects to the session beans as arguments like:

public interface Foo {
 public void doStuff(Bar bar);
}

public class Bar {
 public Integer baz;
 public String wox;
}

I get an "argument mismatch" exception when I try to invoke that session bean from a web application .war file. The problem, as I see it, is that the doStuff() method implementation expects a Bar class loaded with the JBoss unified classloader, while my web app war file is using a WebappClassloader. How am I supposed to fix that problem? Should I tell my in-Jboss tomcat to load all classes using it's own classloader or do I have to do something else?

I haven't added any additional jboss configuration than the default (using 4.0.4RC1). Can someone help me?

[bdecoste]

Try deploying the .war and .jar in an .ear - you should have no problems.

[bdecoste]

Your Bar class is not Serializable. It needs to be.

[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...

[marcwimmer]

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

[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.