Yes Is johnzon snapshot working for you or do you need some backports?
Le 1 déc. 2017 21:48, "Alex The Rocker" <alex.m3...@gmail.com> a écrit : > Hello Romain, > > Thanks for your answer, I created: > > https://issues.apache.org/jira/browse/TOMEE-2153 > > for asking the dependency upgrade of Johnzon in TomEE, and: > > https://issues.apache.org/jira/browse/JOHNZON-149 > > for asking the release of Johnzon 1.0.1 > > I hope this is the right way. > > Best regards, > Alexandre > > > 2017-12-01 13:52 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > > Hi, > > > > 2017-12-01 13:17 GMT+01:00 Alex The Rocker <alex.m3...@gmail.com>: > >> Hi Romain, > >> > >> Thanks, I will give it a try. > >> > >> Back to TomEE+ 7.0.5 : should I fill a JIRA to ask upgrade of Johnzon > >> dependency from 1.0.0 to 1.0.1 (or to any version that fixes > >> JOHNZON-101) ? > > > > you can be johnzon should release a 1.0.1 before tomee tackles it - so > > probably a ticket on johnzon too. > > > >> > >> Best regards, > >> > >> > >> 2017-11-30 7:50 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > >>> openejb.classloader.forced-load=org.apache.johnzon can be a good try > >>> but the API can't be changed for sure > >>> > >>> Romain Manni-Bucau > >>> @rmannibucau | Blog | Old Blog | Github | LinkedIn > >>> > >>> > >>> 2017-11-30 7:48 GMT+01:00 Paul Carter-Brown < > paul.carter-br...@smilecoms.com>: > >>>> Hi Alex > >>>> > >>>> I don't think it will be possible to get the system classloader to use > >>>> johnzon in a war. > >>>> > >>>> Not ideal for you but here are some options: > >>>> > >>>> Include a .bat and .sh to the installer which they must run to > install your > >>>> war. This script can extract your johnzon jars into tomee/lib and then > >>>> install the war. > >>>> > >>>> Alternatively distribute your app as a docker image with everything > >>>> perfectly set up and ready to run. I guess this option depends on > whether > >>>> your war is one of many to be deployed to tomee. > >>>> > >>>> Paul > >>>> > >>>> Paul > >>>> > >>>> Sent from my phone. Message may be brief and contain typos. > >>>> > >>>> > >>>> On 30 Nov 2017 01:12, "Alex The Rocker" <alex.m3...@gmail.com> wrote: > >>>> > >>>>> Hello Paul, > >>>>> > >>>>> I am in a situation where I am not redistributing TomEE+, but only a > >>>>> WAR file, into which I plan to include latest version of Apache > >>>>> Johnzon jar files. > >>>>> > >>>>> So my question is really : will TomEE+ use by default the Apache > >>>>> Johnzon .jar file found in my WAR instead of the ones it has in its > >>>>> tomee/lib directory, or do I need to instruct the people who will > >>>>> install my WAR file to modify some Tomee+ configuration files in > order > >>>>> to instruct TomEE to load my WAR's jars instead of its jars? > >>>>> > >>>>> Best regards, > >>>>> Alexandre > >>>>> > >>>>> > >>>>> 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 > >>>>> >> > >>>>> > >>>> > >>>> -- > >>>> > >>>> > >>>> This email is subject to the disclaimer of Smile Communications at > http://www.smilecoms.com/home/email-disclaimer/ <http://www.smilecoms.com/ > disclaimer> > >>>> >
