Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

https://github.com/tomitribe/tribestream-api-registry/tree/master/tribestream-api-registry-webapp uses jackson 2.8.1 and no issue server config is https://github.com/tomitribe/tribestream-api-registry/blob/master/tribestream-api-registry-webapp/src/main/webapp/WEB-INF/openejb-jar.xml is you hit j

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

I never got this working all my ITs are broken. :-( On Fri, Dec 16, 2016 at 6:53 PM, alexdron wrote: > Romain, > Do you know if that was resolved? > > I have a similar issue. Jackson provider v2.1.5 was working perfectly fine > along with Tomee Plus 7.0.1 until we upgraded jackson-jaxrs-json-

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Romain, Do you know if that was resolved? I have a similar issue. Jackson provider v2.1.5 was working perfectly fine along with Tomee Plus 7.0.1 until we upgraded jackson-jaxrs-json-provider to version 2.8.5. And for some reason it is not picked anymore by CXF. We extend JacksonJaxbJsonProvider a

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Le 22 nov. 2016 02:27, "jieryn" a écrit : > > Yes, I still see it listed. Can I just disable Johnzon so I can get my > Arq tests back and working again? It would be the easiest solution at > this point, I hope.. > Dont think so but first time it is not a 5mn fix. Can you share a failling arquilli

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Yes, I still see it listed. Can I just disable Johnzon so I can get my Arq tests back and working again? It would be the easiest solution at this point, I hope.. On Thu, Nov 17, 2016 at 1:56 PM, Romain Manni-Bucau wrote: > Do you see it listed in the providers i startup logs? it should be sorted

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Do you see it listed in the providers i startup logs? it should be sorted and johnzon is after user providers if they have the same media type. All the dicussion we had was for server providers, for client ones you need to register it on the client. Romain Manni-Bucau @rmannibucau

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Ok, I see what you mean, but Johnzon is still getting invoked even after I subclassed the JacksonJsonProvider and coded the @Produces/@Consumes with specific media types. public abstract class MyJacksonProviderApplication extends Application { @Override public Set getSingletons() { return

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

then add it too ;) point is to not use the default jackson one which is */* */* = lower priority ever Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

I have to support application/xml too though. On Thu, Nov 17, 2016 at 12:39 PM, Romain Manni-Bucau wrote: > replace jackson provider by: > > @Provider > @Consumes("application/json") > @Provides("application/json") > public class MyProvider extends JacksonXXXProvider {} > > And register this prov

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

replace jackson provider by: @Provider @Consumes("application/json") @Provides("application/json") public class MyProvider extends JacksonXXXProvider {} And register this provider instead of jackson one Romain Manni-Bucau @rmannibucau | Blog

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

I think I am doing that, sorry I didn't include it.. import javax.xml.bind.annotation.*; import javax.ejb.*; import javax.ws.rs.*; import javax.ws.rs.core.*; @XmlAccessorType(XmlAccessType.FIELD) @XmlRootElement public class My { private String message; public final String getMessage() {

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

2016-11-17 18:12 GMT+01:00 jieryn : > Yah, I am hard forcing the JacksonJsonProvider: > > import java.util.*; > import javax.ws.rs.ApplicationPath; > import javax.ws.rs.core.Application; > import com.fasterxml.jackson.databind.ObjectMapper; > import com.fasterxml.jackson.jaxrs.json.JacksonJsonProv

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Yah, I am hard forcing the JacksonJsonProvider: import java.util.*; import javax.ws.rs.ApplicationPath; import javax.ws.rs.core.Application; import com.fasterxml.jackson.databind.ObjectMapper; import com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider; public abstract class JacksonProviderApplic

Re: TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Hi Jackson is buggy in its consumes/produces type. Wrap the provider forcing it to application/json lr other but not wildcard Le 11 nov. 2016 21:50, "jieryn" a écrit : > Hi, I'm hitting another migration issue. With 1.7, we see these providers: > > INFO: Using providers: > Nov 11, 2016 3:43:19

TomEE 1.7 -> 7.x migration - Arquillian and JAX-RS providers

Hi, I'm hitting another migration issue. With 1.7, we see these providers: INFO: Using providers: Nov 11, 2016 3:43:19 PM org.apache.openejb.server.cxf.rs.CxfRsHttpListener configureFactory INFO: com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider@3703a400 Nov 11, 2016 3:43:19 PM org.apache.