Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is calling a remote @remote interface from within the same EJB-JAR or EAR would make the app server use RMI/RMI-IIOP?
Or the App Servers would be much intelligent and doing this call locally as if it calls a @local interface???
The container should not do a truly @local call because @local call pass by reference and @remote calls pass by value. However the container can optimise the @remote call so that the full RMI/IIOP network stack is not hit. As I recall WebSphere does such “local” optimisations, I can’t speak to other vendors.
[History: Way back in early pre EJB3 versions of WebSphere there was an option to enable the moral equivalent of the “make @remote look like @local” but I don’t think later version do offer this.]