Re: JSONB Capabilities Broken in 7.1.1 Plume?

[Cesar Hernandez]

Hi, I updated the JIRA ticket with the following:

Hi David Gannon

I did a first swing catching up with this issue.

By looking at the release notes for 7.1.1 (
https://issues.apache.org/jira/projects/TOMEE/versions/12344119) I see two
potential related commits:

Update TomEE with Johnzon 1.0.2
https://issues.apache.org/jira/browse/TOMEE-2276
DateTimeParseException Regression when upgrading to TomEE 7.1.0
https://issues.apache.org/jira/browse/TOMEE-2233,
https://github.com/apache/tomee/pull/162,
https://github.com/apache/tomee/pull/227
Since you provided a finely detailed repro maven project, now the ToDo is
to test the 7.1.1 branch against your project removing one change at the
time.

I'm not familiar with the code from Johnzon but will be happy to start
digging in if the upgrade to Johonzon is the root cause, if not then my
plan is to study and understand the issue solved by Richard Zowalla in
TomEE-2233.

El mié., 10 jul. 2019 a las 13:11, daveg-iwd ()
escribió:

> I went ahead and opened an issue on JIRA.  I included an example project as
> an upload. Hope that's OK.
>
> https://issues.apache.org/jira/browse/TOMEE-2565
> 
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
>


-- 
Atentamente:
César Hernández.

Re: Working around johnzon REST implementation

[Cesar Hernandez]

With the information you provided, it seems that you configurations it's ok.

To have a point of comparison, you can take a look at the example we have:
https://github.com/apache/tomee/tree/master/examples/jaxrs-json-provider-jettison
and also to this article:
https://www.tomitribe.com/blog/upgrading-tomee-keeping-jettison-as-the-json-provider-in-jax-rs/

El mar., 2 jul. 2019 a las 11:44, Jay Leggett ()
escribió:

> We upgraded from 1.7.4 to 7.1.0, and we’re in the process of testing.  We
> came across a problem (see error below) related to the new johnzon
> implementation.  To work around the problem, we’re attempting to revert
> back to the previous implementation by adding resources.xml and
> openejb-jar.xml.  With the changes, the application now starts fine, but
> we’re now getting 404s when making a POST request.  Any thoughts on what’s
> causing the 404?
>
>
>
> resources.xml
>
> 
>
> 
>
>  class-name="org.apache.cxf.jaxrs.provider.json.JSONProvider">
>
> 
>
> 
>
>
>
> openejb-jar.xml
>
> 
>
> http://www.openejb.org/openejb-jar/1.1;>
>
> 
>
> 
>
> cxf.jaxrs.providers = oldprovider
>
> 
>
> 
>
> 
>
>
>
> *Johnzon error*
>
>  at
> org.apache.johnzon.core.JsonGeneratorImpl.close(JsonGeneratorImpl.java:454)
>
> at org.apache.johnzon.mapper.Mapper.writeObject(Mapper.java:147)
>
> at org.apache.johnzon.mapper.Mapper.writeObject(Mapper.java:182)
>
> at
> org.apache.johnzon.jsonb.JohnzonJsonb.toJson(JohnzonJsonb.java:317)
>
> at
> org.apache.johnzon.jaxrs.jsonb.jaxrs.JsonbJaxrsProvider.writeTo(JsonbJaxrsProvider.java:171)
>
> at
> org.apache.cxf.jaxrs.utils.JAXRSUtils.writeMessageBody(JAXRSUtils.java:1417)
>
> at
> org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor.serializeMessage(JAXRSOutInterceptor.java:245)
>
>
> --
>
> *Jay Leggett*
> Software Engineer
> Lenovo United States
>
> [image: Phone](919) 237-8165
> [image: Email]jlegg...@lenovo.com 
>
>
>
>
>
> [image: RedLogo]
>
>
>
>
>


-- 
Atentamente:
César Hernández.