You will have to place the jbossall-client.jar file (which you can find in
%JBOSS_HOME%\client folder) in the classpath of the client.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149311#4149311
Reply to the post :
Thanks for the info. I can go astep further. But now I get another exception as
follow, seems it is a problem of compatability:
Caused by: java.io.InvalidClassException: org.jboss.ejb3.LocalProxy; local
class incompatible: stream classdesc serialVersionUID = -6521545933800264895,
local class
Are you sure you copied the correct version of the jar file? The
jbossall-client.jar file should be the same as the one on the server. And do
you have any other JBoss jar files in the client classpath?
View the original post :
The exception of compatabability obve is resolved.
Client
Now I got another exception:
Exception in thread main javax.ejb.EJBException: Invalid invocation of local
interface (null container)
at
org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:77)
at
Here is all my codes:
MyBeanLocal.java
@Local
public interface MyBeanLocal {
public String test(String text);
}
TestMyBean.java
***
@Stateless
public class TestMyBean implements MyBeanLocal {
public static final String LocalJNDIName =
You cannot use an Local interface from a remote client (the standalone java
client, running in its own JVM). You will require a remote interface for the
bean. Use an interface with @Remote.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149336#4149336
Reply
jaikiran wrote : You cannot use an Local interface from a remote client (the
standalone java client, running in its own JVM). You will require a remote
interface for the bean. Use an interface with @Remote.
You are right. Now I change the Local to remote as follow:
MyBeanLocal.java
You probably are not using the correct jndi-name while doing the lookup in the
client. Use the JNDIView
http://wiki.jboss.org/wiki/DisplayTheJNDITreeWithTheJMXConsole to list the
contents of the jndi-tree and see what's the jndi-name for your bean.
Alternately, you can annotate the bean to
Here is the list. Where can I find the correct jndi-name?
Besides, I try your alternativ but I get Exception of MyJNDIName not bound.
Global JNDI Namespace
+- TopicConnectionFactory (class: org.jboss.naming.LinkRefPair)
+- jmx (class: org.jnp.interfaces.NamingContext)
| +- invoker
anonymous wrote : +- TestMyBean (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy65 implements interface
com.wei.chen.MyBeanLocal,interface org.jboss.ejb3.JBossProxy,interface
javax.ejb.EJBLocalObject)
Here's the jndi-name. You should use TestMyBean/local in the client
I see in the list folowings:
| +- TestMyBean (class: org.jnp.interfaces.NamingContext)
| | +- local (proxy: $Proxy65 implements interface
com.wei.chen.MyBeanLocal,interface org.jboss.ejb3.JBossProxy,interface
|
It is still local though I've changed to remote in my codes.
How can I
thomas2008ch wrote :
|
| How can I overcome it?
Make sure that your changes to the bean and its interfaces are being picked up.
Compile those classes, recreate the jar and then clean the existing jar from
the JBoss deploy folder and deploy this new jar file.
View the original post :
jaikiran wrote : anonymous wrote : +- TestMyBean (class:
org.jnp.interfaces.NamingContext)
| | | +- local (proxy: $Proxy65 implements interface
com.wei.chen.MyBeanLocal,interface org.jboss.ejb3.JBossProxy,interface
javax.ejb.EJBLocalObject)
|
| By the way, are you sure that your
I got it.
Many thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4149366#4149366
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4149366
___
jboss-user mailing list
14 matches
Mail list logo
