Access EJB from different app server

[brijesh chavda]

Hi,

I have a JSF web application which is deployed on Glassfish server and i have EJB 3 components deployed on weblogic 10 server. How can i call those EJBs from the JSF managed beans.
I tried to use InitialContext by setting context factory to weblogic context factory and putting wlclient.jar in the classpath of JSF web app. It doesnt work. JSF application is failed to deploy.

Is there something i am missing.

Any quick help is really really appreciable.

Thanks,
Brijesh

[K Kiran Kumar]

Hi Brijesh,

I hope you are trying to call the Bean that implemented the Remote interface. I have done using WebSphere. I guess the logic should be the same. Can you please use the below code and try to call the EJB method.

public void callEjbMeth()
{
        String initialContextFactory = "com.ibm.websphere.naming.WsnInitialContextFactory";   // You might have to modify this to accomodate for Weblogic.
        String providerUrl = "corbaloc:iiop:localhost:2809";   //modify this properly
        Hashtable<String, String> environment = new Hashtable<String, String>();   
        environment.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);   
        environment.put(Context.PROVIDER_URL, providerUrl);   
        try 
        {   
            Context ctx = new InitialContext (environment);   
            StateLessBeanRemote remote = (StateLessBeanRemote) ctx.lookup("a.b.c.d.StateLessBeanRemote");   
            System.out.println(remote.getRemoteMethod()+"**********");
        } 
        catch (NamingException e)
        {   
            e.printStackTrace();   
        }  
}

[brijesh chavda]

Hi Kiran,

Yes thats what i tried. I put the weblogic context factory in the properties and put wlclient.jar in classpath of glassfish (I tried putting it in lib folder of my WEB-INF too.) . It looks like weblogic client jar is creating some conflicts with glassfish. My application failed to deploy.
If i remove wlclient.jar, Application deploys fine without error.

Thanks,
Brijesh

[Claude Moore]

It looks like weblogic client jar is creating some conflicts with glassfish. My application failed to deploy.

It doesn't sound new to me. Years ago, I tried a similar approach (let two different appserver talk each to other using EJBs) and after a while I gave up. Since my application servers were in LAN, and I did not need a lot of different services to be used by each other, I used webservices instead, and that approach worked.

It's a pity. EJBs are powerful and I like them a lot, but in my humble opinion when you're using them outside the appserver there are always troubles (lot of jars on the client side to be deployed, jar conflicts and others).

I'm sorry to not be able to advice you better, but I think you'd better try webservices to avoid such issues. No headaches :-)