This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Yes you are right, if your webcontainer and EJB container run in the same JVM you can use local interfacing. In WAS 5 each application server has it own JVM. So if your web container and ejb container are in the same application server they are in the same JVM. This also means that if you have multiple applications deployed in the same application server they also run in the same JVM.
We've got a clustered environment with two (maybe three) machines with 2 WAS instances on it. So we've got 4, maybe 6 WAS instances with the whole application deployed on each WAS instance. There's a load balancer taking care of balancing the load of all requests to the WAS instances.
Is there any reason to use Remote SLSB's (being called from the web app)?
Hi Ruud, Local vs Remote interfaces?.....mmm... The methods in your ejb's are reusable or may become reusable by another application in the future? if that's the case then you should implement remote interface. But if the methods in your ejb's are only used by your webmodule then you should implement local interface so you can get better performance. I see no complication by implementing local & remote interfaces, that way you could use local interfaces for now, and when the time comes for an application to use your ejb's methods, they could get them using the already implemented remote interface.
Consider the fact that remote interface is more expensive in performance that local interface.
SCJP 1.4, <br />IBM Certified System Administrator Websphere Application Server 5.0, IBM Certified DB2 UDB Database Associate