yes and no. How do you replace tomee EJB implementation? you can't. JPA is quite particular cause not that portable at the end usage but except JSF other specs are very portable.
However, keep in mind that in the case of JSON, you can always replace johnzon implementation since some years. You just need to set both implementations as inactive (through the .active=false system prop) and add your custom global ones to the user system property. So to summarize: 1. you can use any custom json provider from your app 2. you can use any custom provider globally for all apps 3. you can setup any custom provider programmatically through an extension mecanism if you prefer 4. you can ignore johnzon configuring it as ignored This is why I'm not really following you and I don't understand what you are trying to achieve Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le lun. 24 sept. 2018 à 15:44, exabrial12 <exabr...@gmail.com> a écrit : > I think I understand the disconnect. See TomEE plume allows for completely > removing OpenJPA and replacing it with EclipseLink, because the non-spec > behavior of EclipseLink (especially their JMS based cache-invalidation and > ID batch fetching) is very useful. Similarly, we want to completely replace > Johnzon at the server level because it's non-spec behavior is very useful. > > Again, this doesn't modify the default behavior of TomEE and provides a > useful extension point to developers. > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
