Re: Using non-default JsonProvider

2017-06-05 Thread Romain Manni-Bucau
should be done (think our messages were "concurrently sent" :)) PS: if you want to hit johnzon list as well to share why you needed to switch it can allow to avoid this need (theorically you shouldnt be able to switch impls in a EE server and if johnzon has a real gap we need to tackle it)

Re: Using non-default JsonProvider

2017-06-05 Thread Svetlin Zarev
Hi, I've tested it and it works like a charm ! may you add johnzon to the filter list ? Thanks and best regards, Svetlin 2017-06-05 12:39 GMT+03:00 Romain Manni-Bucau : > Hi Svetlin, > > we can add jsonp in > https://github.com/apache/tomee/blob/master/container/ >

Re: Using non-default JsonProvider

2017-06-05 Thread Romain Manni-Bucau
Hi Svetlin, we can add jsonp in https://github.com/apache/tomee/blob/master/container/openejb-core/src/main/java/org/apache/openejb/util/classloader/URLClassLoaderFirst.java#L569 list to ensure the behavior you desire work (but note we respect the spec in our current behavior). Can be

Using non-default JsonProvider

2017-06-05 Thread Svetlin Zarev
Hi, If the application brings its own JsonProvider, then JsonProvider.provider() should return it instead of the default one. Instead TomEE always returns the default one (Johnzon). The issue is that JsonProvider.doLoadProvider() returns the first encountered one and does not check if it's the