Thanks for the reply joe!I am able to do it!But i have some confusion regarding ejb deployment and all(For standalone application).I wrote a bean and exported it as jar(Advice.jar)(having interfaces+bean class+deployment descriptor).Then i ran a weblogic command to generate the client side jar(ejb_client.jar) having stubs and interfaces implementation.Then i wrote my client application(client
java program+interfaces and bean class to avoid compilation error) and added that client jar to the classpath.Then i deployed that jar(advice.jar) to weblogic.Then i ran the command (j
ava -Djava.naming.factory.initial=weblogic.jndi.WLInitialContextFactory -Djava.naming.provider.url=t3://localhost:7001 -cp C:\bea10\wlserver_10.3\server\lib\weblogic.jar;.;ejb_client.jar EjbClient) where EjbClient.java is my client program.I am using t3 protocol to connect to my server and i got the output.
Here are some of my doubts(some might look weird but i want to know)....
1)If the application is talking to the deployed jar on server through t3 then what is the need of ejb_client.jar
2)I tried replacing ejb_client.jar with Advice.jar even then also it worked.why?
3)I used to think that once i'll get the ejb_client.jar.I can directly use it in my classpath without any server(seems weird
) because that jar is having the interfaces implemented).
I also tried it with web application.i wrote a simple jsp and servlet +interfaces and bean class in order to avoid compilation errors and i deployed it on server while bean jar(Advcie.jar) already being on server and it worked fine(looks good to me).
Please sail me out.Could anyBody make my fundamentals clear over it.Please.......Thanks in Advance.