This trick can be used for johnzon https://rmannibucau.wordpress.com/2013/07/19/little-tip-to-help-you-to-test-javaee-7-in-tomee-with-tomee-maven-plugin/
side note: don't forget to upgrade jsonp and jsonb api jar as well. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-29 13:08 GMT+01:00 Paul Carter-Brown <paul.carter-br...@opposablethumbs.io>: > The 3 Johnzon jars sit in tomee/lib/ directory. You can delete the old ones > and copy in the new ones built from source. Works for me. > > On Wed, Nov 29, 2017 at 1:32 PM, Alex The Rocker <alex.m3...@gmail.com> > wrote: > >> Hello, >> >> While upgrading one of our webapp from TomEE+ 1.7 to TomEE+ 7, we hit >> a regression on JAX-RS. >> >> After analysis, we found that we've been impacted by the same issue as >> the one fixed in this JIRA: >> https://issues.apache.org/jira/browse/JOHNZON-101 >> >> We would like anyway to move to TomEE+ 7.0.4, but without waiting for >> a future TomEE+ 7.x that would include this Johnzon fix. >> >> We tried to package a more recent version of Johnzon into our web app, >> but it seems that it wasn't take into account by TomEE's JAX-RS >> engine. >> >> What is the right way to get TomEE+ use the more recent Johnzon JARs >> when it's packaged in a WAR ? >> >> Best regards, >> Alex >>
