Oops my bad: please read in my previous mail that I just opened JOHNZON-160: https://issues.apache.org/jira/browse/JOHNZON-160?jql=text%20~%20%22MapperException%22
Thanks, Alexandre 2018-03-04 15:08 GMT+01:00 Alex The Rocker <alex.m3...@gmail.com>: > Hello Romain & Mark, > > Yes I already filled a generic JIRA JOHNZON-149 a while ago for asking > Johnzon upgrade to 1.1.x in TomEE 7.0.5. > > And I just filled JOHNZON-105 with a more specific JSON-B/Mapper issue: > https://issues.apache.org/jira/projects/JOHNZON/issues/JOHNZON-105?filter=allopenissues > > It would be great to have a fix for it in upcoming TomEE 7.0.5, along > with latest security updates on embedded components (Tomcat, etc..) > > I will provide feedbacks with our large & complex web apps as soon as > there's something testable as a snapshot (or I can built stuff with > Maven, but i'll need by steps to make sure I'm pointing to appropriate > repos/versions/tags) > > Best regards, > Alex > > > 2018-03-04 14:46 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: >> @Mark: it is tracked on johnzon ( >> https://issues.apache.org/jira/plugins/servlet/mobile#issue/JOHNZON-149). >> There was the proposal I did months ago to just use jsonp/b 1.1/1.0 in >> tomee 7 (doesnt prevent anything from tomee perspective if we drop java 7 >> compat). If not desired we should redo 1.x from master pby to avoid an half >> merged branch. >> >> Le 4 mars 2018 12:40, "Mark Struberg" <strub...@yahoo.de.invalid> a écrit : >> >>> Hi Alex! >>> >>> johnzon-1.0.x is targetting JSON-P_1.0 (EE7) and johnzon-1.0.0 is indeed >>> the last version we shipped so far. >>> >>> johnzon-1.1.x is targetting JSON-P_1.1 and JSON-B_1.0. >>> Those are all EE8 specs and thus this is also the version used in TomEE8. >>> >>> If you have some urgent need/request for a fix in Johnzon-1.0.x (EE7) then >>> please identify the tickets you suggest to have fixed and report them on >>> the d...@johnzon.apache.org list. >>> What could work is if you go through either the tickets resolved in >>> various johnzon-1.1.x versions, or scan the git log for fixes you want to >>> have backported. >>> We will then discuss it over there, create tickets and then merge back the >>> stuff. >>> The Johnzon team is surely happy about every helping hand! >>> >>> Btw, that's really the same for almost all the parts of TomEE. >>> 85% of the tickets and improvements are really happening at all the other >>> projects: johnzon, bval, OpenWebBeans, OpenJPA, MyFaces, Tomcat, Geronimo, >>> etc. >>> >>> Of course it's a good idea to keep the TomEE project in the loop from a >>> high-level perspective. For example to summarise the tickets which will get >>> resolved. >>> But the actual work + the release etc will happen on the Johnzon, OWB, etc >>> lists. >>> >>> txs and LieGrue, >>> strub >>> >>> >>> >>> > Am 03.03.2018 um 23:32 schrieb Alex The Rocker <alex.m3...@gmail.com>: >>> > >>> > Hello, >>> > >>> > +1 for a TomEE+ 7.0.5 asap, I volonteer to test it against our large web >>> apps! >>> > By the way, TomEE+ 7.0.4 had a super old version of Johnzon (1.0.0 if >>> > I remember well), could 7.0.5 embedded a decently more recent Johnzon >>> > version to fix the tons of issues we had to hack around with Johnzon >>> > 1.0.0 ? >>> > >>> > Thanks, >>> > Alex >>> > >>> > 2018-03-02 14:56 GMT+01:00 Mark Struberg <strub...@yahoo.de.invalid>: >>> >> hi folks! >>> >> >>> >> We discussed this quite some times and we got good feedback so far. So >>> it's finally time to make this reality. >>> >> >>> >> Over the weekend I'd like to switch TomEE to master and create a >>> maintenance branch for Tomee7. >>> >> >>> >> After that I'd love to roll a first TomEE8 version in say one month >>> from now. >>> >> >>> >> Any objection? >>> >> >>> >> >>> >> LieGrue, >>> >> strub >>> >> >>> >>>
