• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

java.lang.NoSuchMethodError: HandlerMethodResolver

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've a web application using spring 3.0.5 and Tomcat 6.0.16

The following exception occurs in the browser when trying to access the application




The pom.xml :




Many thanks in advance !!!
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not sure why you posted the pom file.

Anyway, is there more to that stack trace. It looks like you didn't paste the entire stack trace. Look at the very bottom of your stack trace to find the root cause exception and post that please.

Thanks

Mark
 
Frank VanOor
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Mark, thanks for reply. The full stacktrace is in the log file localhost.2011-06-07.log in the directory logs from tomcat.

 
Ranch Hand
Posts: 433
Netbeans IDE
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You are facing some version-clashes.
Try to exclude the spring-context dependency from spring-tomcat-weaver:


and use the current version of webflow (if possible):



Maybe there are more clashes but those are the ones I could spot.
 
Frank VanOor
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Joachim , thanks for suggestion.

I removed spring-tomcat-weaver , it compiled fine but still have the same exception.

I didn't find version 2.3.0 of spring-webflow. The version I found is 1.0.6. I added this version, but still same exception.

 
Mark Spritzler
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Frank VanOor wrote:Hi Joachim , thanks for suggestion.

I removed spring-tomcat-weaver , it compiled fine but still have the same exception.

I didn't find version 2.3.0 of spring-webflow. The version I found is 1.0.6. I added this version, but still same exception.



When you build, in your target directory, what are the third party jars that get packaged with your application. Look at them and tell us if you see any duplicates with different version numbers.

Mark
 
Joachim Rohde
Ranch Hand
Posts: 433
Netbeans IDE
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Have you considered that the groupId changed for the new SpringWebFlow versions?
But as Mark mentioned: it would be best to have a look in your target directory for duplicates.
 
Frank VanOor
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
H Mark,

You were right !!! I looked into the Target directory and indeed, lots of Spring 2.5.6 jars were still sitting there. I did a maven clean which removes the content of Target, made a new build, deploy and the Exception isn't happening anymore.

Many many thanks !!!

 
Mark Spritzler
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Frank VanOor wrote:H Mark,

You were right !!! I looked into the Target directory and indeed, lots of Spring 2.5.6 jars were still sitting there. I did a maven clean which removes the content of Target, made a new build, deploy and the Exception isn't happening anymore.

Many many thanks !!!



It was definitely a team effort.

Mark
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic