• 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
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Spring framework and Guava version compatability

 
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As the bug reported here: https://nvd.nist.gov/vuln/detail/CVE-2018-1199 I am upgrading Spring in my project as follows: Spring framework from 4.3.10 to 4.3.16; Spring security from 4.2.3 to 4.2.4;
I am able to make the build successfully with upgraded new version, but it gives following error when I deploy this build on Tomact: java.lang.NoClassDefFoundError: com/google/common/collect/ImmutableAsList
I use Guava version, which is 12.0.0 in my project. I tried to upgrade this Guava version from 12.0.0 to 16.0 or 19.0, 24.1-jre ; but then it gives compilation error in my existing code for the following import:

import javax.annotation.concurrent.Immutable;

Can someone please suggest me, what could be the possible fix for this error I get here. I am absolutely clueless.
If I could know:: Which version for Guava is compatible with SPRING4.3.16 & JDK1.7. That will help me to get solution.

Thank you for your time to reading my question.
 
Ramesh Kumar Swarnkar
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The error message is misleading. Because the Spring configuration file was looking for log4j property file which cannot be found. When I added the log4j property files, the spring context could inject it in the declared element and went fine now. Thanks !
 
You don't like waffles? Well, do you like this tiny ad?
Garden Master Course kickstarter
https://coderanch.com/t/754577/Garden-Master-kickstarter
reply
    Bookmark Topic Watch Topic
  • New Topic