If you are deploying an application to Tomcat server that is running inside JBoss, then you do not need to include jbossall-client.jar. This jar file is for clients that are not deployed in JBoss and that want to use JBoss classes.
make sense? cgriffith
No, I'm using a standalone tomcat that makes remote invokations to the jboss application server.
In that case, try to use another client jar available in $JBOSS_HOME/client directory. Like jboss-client.jar. I guess jbossall-client.jar can not be used in a WAR.
I tried the following:
I deleted the jbossall-client.jar from my lib directory. I added the following 4 files (I tried as long as no more ClassNotFound or NOClassDefFound exception occurred):
Since I use the Spring project (IoC), I get CommunicationExceptions:
javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.invocation.InvokerInterceptor; unable to create instance] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
Can anyone help me?
The problem is solved. With JBoss 4.0.4 RC 1, the problem doesn't occur because the jbossall-client.jar does no longer contain the javax.servlet classes!
I think that is was an error in the jboss internal packaging process.
i have problem as same as yours.
is any solution for that prob beside change my Datasource server version to Jboss 4.0.4 rc1?
I've a similar problem. Did you find out which client libraries we should use to connect to jboss 4.0.3 ?
I could really use your help:(
Same problem here, any suggestions?