• Post Reply Bookmark Topic Watch Topic
  • New Topic

SEVERE: Exception sending context initialized event to listene - java.lang.VerifyError  RSS feed

 
Rodrigo Bossini
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
At first I had created a standard JSE project, which had the main method to start running.

Then I created a web project so I could start my JSE project from within tomcat.

I added a simple Context Listener to the web project, which in its contextInitializedEvent simply does the same thing that the old main method would.

Here's my contextInitializedMethod:



And here's the go method from the NovoSMS class:


Here's the error I get when it gets to the gerente = new GerenciaExecucao("A path to an actual directory"); line:


I created a new constructor to the GerenciaExecucao class which does nothing, just for debugging. Same exact thing Happens. Has anyone seen this error before?
 
Ernest Friedman-Hill
author and iconoclast
Sheriff
Posts: 24217
38
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This kind of error often means that you're compiling your classes against one version of a library, but then are running them using a different (earlier or later) version. Check all the libraries you're using in both places o make sure everything is up to date.
 
Rodrigo Bossini
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ernest Friedman-Hill wrote:This kind of error often means that you're compiling your classes against one version of a library, but then are running them using a different (earlier or later) version. Check all the libraries you're using in both places o make sure everything is up to date.


Thank you. I indeed had first compiled my project with java 6 and then installed java 6 (and left both 5 and 6 installed). I then compiled it again, which probably made it to happen.

Wouldn't this be the right time for "retrocompatibility" play its role?
 
Rodrigo Bossini
Ranch Hand
Posts: 113
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ernest Friedman-Hill wrote:This kind of error often means that you're compiling your classes against one version of a library, but then are running them using a different (earlier or later) version. Check all the libraries you're using in both places o make sure everything is up to date.


Can you provide further assistance?

Here's what I did. Delete all of the java versions that I had installed and deleted Eclipse as well.

Installed java 5u22(because that's what they use in production here).

Then I reinstalled Eclipse and reset the OS classpath.

Deleted the .class files from my project and rebuilt it.

Result: Same problem.

What else could I do?

PS: I verified in project properties that Xdoclet was missing. Then I downloaded it and pointed eclipse to the jar file. Could that have anything to do with this problem?

What else do I do?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!