you have the same look of the interface, but one is com.DataProtection and one is src.interfaces.DataProtection.
This is for me and for Java not the same interface!
You should use the same source or interface.jar file for your Web-App!!
Also your code new InitialContext() ....
might be easier if you use
@EJB DataProtection manager
and let do the container the work for you
the annotation is not good because the variable is null.
i changed my packagenaming in the bean and now the constructor is ok, but i get another error if i try to call the method.
15:56:54,122 ERROR [STDERR] java.lang.RuntimeException: Could not resolve beanClass method from proxy call
15:56:54,122 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:274)
15:56:54,122 ERROR [STDERR] at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81)
15:56:54,122 ERROR [STDERR] at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72)
15:56:54,122 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
Can you eventually solve this problem too? :-)
Sounds like a similar problem.
The method will be found by the signature, could it be that your AdressIdType is also different?
I recommend that you use the interface.jar file for your application.
Two choices, pack the jar into your WAR file or copy to the server/.../lib directory.
Also it is possible to use the default JBoss classloader (no loder-repository tag in your app), in this case all classes are shared between different deployment files.
Thanks a lot. Now everthing is fine.