Session bean , Local and Remote interface with answer.

[Deepak Jain]

As we know that a session bean can avoid implementing the busniess interface by applying say Local or Remote
annotation to the class itself as follows

package com.ejb3inaction.actionbazaar.test;
 
import javax.ejb.Remote;
import javax.ejb.Stateless;
 
@Stateless
@Remote(TestRemote.class)
public class TestBean {
public void method1() {
System.out.println("Start:TestBean.method1()");
System.out.println("End:TestBean.method1()");
}
}
 

package com.ejb3inaction.actionbazaar.test;
 
import javax.ejb.Remote;
 
@Remote
public interface TestRemote {
public void method1();
public void method2();
}
 
package com.ejb3inaction.actionbazaar.test.client;
 
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
 
import com.ejb3inaction.actionbazaar.test.TestRemote;
 
public class TestClient {
 
/**
 * @param args
 */
public static void main(String[] args) {
// TODO Auto-generated method stub
try {
Context context = new InitialContext();
TestRemote test = (TestRemote)context.lookup("myEJB/TestBean/remote");
test.method1(); // 1
test.method2(); // 2
} catch (NamingException e) {
e.printStackTrace();
}
}
 
}
 

Question and Answer:
Well this time am answering myself.

1) Does this mean that the bean can get away by not implementing all the methods of the interfaces?

Yes its got away, the bean did not implement method2(). The compiler did not complain, since the bean
never implmented TestRemote interface.

2) What happens if the client invokes the buisness interfaces in the above case, which are not implemented by the session bean?

TestBean is deployed, despite not implmenting the method2().
Now when client invokes method2() the following exception is thrown @ the client side
[java] Exception in thread "main" java.lang.RuntimeException: Could not resolve beanClass method from proxy call
[java] at $Proxy0.method2(Unknown Source)
[java] at com.ejb3inaction.actionbazaar.test.client.TestClient.main(TestClient.java:2

[Mellon Sun]

It's a little bit freak.

[Reza Rahman]

Deepak,

The implemenatation are are using appears to be buggy. The deployer should have caught this problem.

Best regards,
Reza

[Deepak Jain]

The implemenatation are are using appears to be buggy. The deployer should have caught this problem.

Hello Rahman,
Its simply a honor getting an opportunity to interact with you.
I could not understand your answer. Are you trying to say that there is a bug in the code or a bug with the Jboss application server.
I am using jboss-4.2.3.GA as my application server.

[Reza Rahman]

Deepak,

Thanks for the kind words. The priviledge is mine, I am just another developer like you - perhaps with slighly different circumstances...

The application server is buggy, but your code is also not spec compliant. If you want, you could open a JIRA issue for JBoss AS.

Best regards,
Reza