Greetings,
I have a question regarding stubs. If I create a bean, it's component interface and it's remote interface, and use deploytool to build the EAR, it gives me back a client JAR. In the client JAR are the stubs to my home and component interfaces.
When I build a client, I obviously need the component and home interfaces on the classpath. This is convenient considering the client JAR resulting from deploytool contains these. However, I also need the stub classes for the client as well.
My question is: does RI handle stubs differently than most other containers out there (e.g.
JBOSS)? Do I need to somehow generate my component and home interface stubs on JBOSS and include them in the classpath of my client, or does JBOSS use that "dynamic proxy" thingy HFEJB refers to?
HFEJB was explicit, stating that the client needs to have access to the stub class files. Does this mean I have to know which server implementation my EJBs are running on so that I can get the "specific" client JAR so that my program will have access to the classes that server uses as it's stub implementation? Furthermore, is RI a "special case" when you absolutely need to create the stubs in the client JAR and include it with your
test client?
TIA for any info!
Cheers,
Jason
[ March 08, 2005: Message edited by: Jason Mowat ]