Ok so to clarify:

1. no "bug" in the stack for your case except that you app uses jaxb to
model json objects which is not clearly specified as required (think you
created a jira on that already)
2. you can use moxy if you follow the rules i mentionned - maybe the not
obvious part is cxf compares *all* types and not each one by one so tomee
application/*+json wins over moxy */*. Try to register:

@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public class Moxy extends MOXyJsonProvider {
}


Le dim. 23 sept. 2018 à 00:47, exabrial12 <exabr...@gmail.com> a écrit :

> > Did you think to
>
> You may be are unaware, but that phrasing is rude. Your question can be
> asked without it. I certainly don't know everything, but that's why I'm
> here.
>
>
> > register your provider on the client and ensure it was handling json?
>
> Yes. It's not being called.
> https://github.com/exabrial/johnzon-univited-guest-topart
>
>
> > Johnzon Buggy
>
> We're dealing with a vendor that doesn't understand how json works. We want
> to use our own provider because johnzon won't parse it.
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>

Reply via email to