I deployed a Stateless Session Bean on Weblogic 8.1 (which is EJB 2.0 compliant). I believe we need the Remote Component Interface and Remote Home Interface stub classes generated by the container are required by the client if we are looking up and invoking a business method on EJB from a remote client (from different JVM).
But I could invoke the EJB from a remote client with only the Remote Component Interface and Home Interface on the classpath of the client (without even getting the stub implementations from the container).
So is this something specific the Weblogic that it provides the stub classes on the fly to the client upon request (a feature similar to downloadable class files)? Or is this feature defined by EJB 2.0 spec?
Do your build (I do it with the wlappcAnt task) which will cause the RMI compiler to run in order to generate the dymamic proxies.
SCJP 1.4, SCWCD 1.3, SCBCD 1.3
posted 14 years ago
I am not using wlappc or any other build utility. I had compiled the interfaces and the bean class by having weblogic.jar on classpath. Then I supplied the client with only compiled Remote Interface and Remote Home Interface (without using weblogic.ejbc EJB compiler for generating stubs).