if jackson changed something about its lifecycle@classloader usage then it can lead to that if part of the app overlapp between the lib part of the ear and the webapps. In TomEE the webapp tries to load from the parent first.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le mer. 6 juin 2018 à 10:44, Dignesh <dgo...@opentext.com> a écrit : > Hello Romain, > > I have deployed an ear , which in turn contains multiple wars. > I have jackson libraries in my webapp. > I have recently upgraded the jackson to jackson 2.9.5 libraries and with > that change I am seeing this issue. > When I revert back to the older version jackson 2.6.6 libraries , i dont > see > the linkage error. I removed the older libraries and replaced with the > newer > one again and i dont see the issue. > This behaviour is something i am not seeing it consistently. > > Just curious to understand how it was working earlier when i had jackson in > webapps and now it is throwing the error. > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
