I have an application built in Spring, deployed on jboss. datasource is defined in a mssql file in jboss/seerver/default/deploy directory. It runs fine.
There is a web service deployed on jboss as well. When my application tries to access the web service, i encounter a ClassNotFoundException for org/jboss/logging logger class. I tried to add the jboss-common-client.jar to my classpath. but when i did i got some jar conflict and at server startup, i started getting jndi exception as if there is no object bound with my datasource name.
I do not understand where <classpath> is defined. That is not a standard JBoss AS setting.
I also don't understand org.jboss.logging.Logger cannot be found since that is part of JBoss AS and thus should be in the classpath for your app automatically, assuming your application is a WARE, EAR or something else like that. Exactly what kind of application is this?
Also, it is usually best to provide the complete stack track rather than just the error message.
Many thanks for replying.
Its actually a simple Spring 3 controller based application(no EJBs) built using MyEclipseForSpring 9. The classpath I sent is the file created by MyEclipse for the project. I thought it would be useful for some one to point out any conflict if there is any among the jars.
Unfortunately, I know very little about the web service I am trying to use, as I haven't coded it myself. It is deployed on the same JBoss-4.2.0.GA. The problem may be related to Spring jars, I am not sure. Kindly direct me if this is not the right forum to post this problem.
My code requests the service for some data. On the web service console, I get a classdefnotfound exception.I dont have the full stack trace right now. I will post it as soon as possible.
It has been years since I worked with Spring and probably all of the stuff I remember is no longer valid. So let's look at this purely from a JBoss AS perspective. You will have to figure out how to convince MyEclipseForSpring to generate what is required.
I assume you have a WAR file. Please post the contents of the WAR file by running "jar -tf path/to/xxx.war" where path/to/xxx.war is the full or relative path to your war file.
Also post the full exception stack trace. Make sure you post the first exception stack trace if there are multiples. Alternately you can attach the root.log and server.log files.