I am currently working with EJB3 and JBoss and I am wondering if anybody knows sth about EJB3 and distributed systems. The interface a remote java client gets from the Namingservice is a plain java interface that does not extend java.rmi.Remote.
a) Why is it working with a standalone client? b) What about a native C++ client?
Does anybody have an answer?
Marco Barenkamp<br />_ _ _ _ _ ________________________ _ _ _ _ _ <br />L M I N T E R N E T S E R V I C E S AG<br /> <br />Head of Software Development<br /> <br /> <br />BEA Certified Enterprise Developer<br />Sun Certified Programmer for the Java2 Platform<br />Sun Certified Web Component Developer for the Java2 Platform<br />Sun Certified Developer for the Java 2 Platform <br />Sun Certified Business Component Developer for the Java 2 Platform <br />Sun Certified Enterprise Architect for the Java 2 Platform Enterprise Edition<br /> <br />LMIS AG
Marco, Currently working on EJB3 on JBOSS??/Does latest version of JBOSS support ejb3.0???
Joined: Aug 27, 2001
yes, JBoss supports EJB3 almost entirely (at least, what has been specified 'til now) plus some enhancements like message driven pojos, simplified packaging for EJB3 entity beans (no need for the *.par archive). You have to install some additional MBean Services like ejb3.deployer and aop-jdk50.deployer, 'cause EJB3 works with Annotations.
But the problem is that they are working with JRMP. With Java5, no stub generation is needed for homogenous systems, but Idon't have a clue what about IIOP. The EJB Spec does not mention anything. It just deals with IIOP and EJB2.1.
The interface is a regular business interface, but the Container-generated implementation class is Remote. The Container has to do all the work under the covers.
b) What about a native C++ client?
IIOP is a different matter. Because the business interface is not Remote there are problems compiling with IIOP. Those who need interop may need to stick with the core EJB model and not use the simplified layer, at last for now.