Configure webapp to use local or remote interface based on environment

Question

Hi,
I have the following problem I am trying to solve (app server is Weblogic 10g by the way).
I have a webapp (war-project) and an ear project containing stateless session beans.
In our development environment I would like to deploy the war and ear separately, because that is easier for development (war-project can then be deployed as a directory, so changes to jsp's and such have immediate effect).
Deploying the war and ear separately means that the war-project can only call the session beans through their remote interfaces. For development this is not a problem.
In a production environment however we would like to package the war INSIDE the ear, so that the webapp can use the local interfaces to call the session beans, as this will improve performance.
So I am looking for a solution where I can configure the way beans are called. Local if the war is inside the ear, remote if the war is separate from the ear. I was thinking along the lines of packaging a properties file with the war that determines the mode (local or remote). Or maybe packaging a different deployment descriptor, if that is a possibility.
This is what I have so far:
Business Interface_
package be.cegeka.test.ejb3.service;
public interface TestService {
     public void doSomething();
Remote Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceRemote extends TestService {
Local Interface_
package be.cegeka.test.ejb3.service;
public interface TestServiceLocal extends TestService {
Bean implementation_
package be.cegeka.test.ejb3.service;
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
@Stateless(mappedName="ejb/TestService")
@Local(TestServiceLocal.class)
@Remote(TestServiceRemote.class)
public class TestServiceBean implements TestService {
     @Override
     public void doSomething() {
          System.out.println("I'm doing something");
     @Override
     public void doSomethingLocal() {
          System.out.println("I'm doing something local");
JSF backing bean_
package be.cegeka.test.ui;
public class MyWebAppBackingBean {
     @EJB(mappedName="ejb/TestService", beanInterface=TestServiceRemote.class)
     private TestService testService;
     public String doSmth() {
          testService.doSomething();
          return "success";
}The part that I would like to be configurable is the "+beanInterface=TestServiceRemote.class+" part in the JSF backing bean. Depending on the environment (development vs. production), this should be "+beanInterface=TestServiceRemote.class+" for development and "+beanInterface=TestServiceLocal.class+" for production.
Is something like this possible?
I would like to avoid having to fill my web.xml with ejb-refs and having to do the JNDI-lookups myself if at all possible, to keep things as easy and clean as possible.
Any ideas are welcome!
Steven

Answer 1

Hey Manish,
comments inline.
"manish kumar" <[email protected]> wrote in message
news:1794338.1102557677925.JavaMail.root@jserv5...
So If they are supposed to be in the same JVM -
then
1. the cluster of 3 weblogic servers are three JVMs. So does that meanLOCAL INTERFACES CAN'T BE USED IN CLUSTERED ENVIORONMENT ?
Sure they can, but the calling component in an enterprise app will not call
an intance of the local bean on another node in the cluster. It will make a
by-reference call to the local component in the same EAR. Local interfaces
are not Remote, so they cannot be used with by-value RMI semantics.
>
2. ARE YOU SURE ABOUT THIS FACT THAT THAT LOCAL INTERFACES CAN BE USEDONLY INSIDE THE SAME APPLICATION, I THOUGHT IT CAN BE USED AS LONG AS CLINET
IS IN THE SAME JVM?
PLEASE CONFIRM.........!!!!!!!!!!!!!Dead sure:
http://e-docs.bea.com/wls/docs81/programming/classloading.html#1073506
http://e-docs.bea.com/wls/docs81/ejb/understanding.html#1126831
http://e-docs.bea.com/wls/docs61/ejb/cmp.html#1085452
http://www.theserverside.com/discussions/thread.tss?thread_id=14628
Also, search the ejb newsgroups. I know Rob Woollen has addressed this in
here somewhere. And, if Rob says it's so, trust me, it's so.
Bill