This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Other Java Products and Servers and the fly likes Runtime Error with new WAR Deployment  - java.lang.verifyError Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » Other Java Products and Servers
Bookmark "Runtime Error with new WAR Deployment  - java.lang.verifyError" Watch "Runtime Error with new WAR Deployment  - java.lang.verifyError" New topic
Author

Runtime Error with new WAR Deployment - java.lang.verifyError

Tony Moses
Greenhorn

Joined: Aug 21, 2002
Posts: 22
I am developing a J2EE app on iAS (Sun ONE) 6.0. I am getting the following error when I try to execute the following line of code:
fillClass = Class.forName(fillClassName);
where fillClassName = xxx/xxx/xxx
java.lang.VeryifyError (class: xxx/xxx/xxx, method: xxxx) Incompatible object argument for function call
The weird thing is that the method referenced in the error isn't even being called.
This error was not occuring until I rebuilt my WAR file to contain all of my java packages/libraries (common components and app specific libraries due to customer requirement). I have read that I need to use javac to prevent this from occuring, but that is waht I do use to compile all of my classes. Can anybody provide any insight as to why this is happening?
When I had my jars referenced in the classpath this error was not occurring.
Michael Ernest
High Plains Drifter
Sheriff

Joined: Oct 25, 2000
Posts: 7292

I've seen this occur when the class in question was available in more than one JAR, particularly when two versions of the same JAR were in the classpath. I'm not aware of a compiler switch that has anything to do with it.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Runtime Error with new WAR Deployment - java.lang.verifyError