2 JIRAs submitted when using Java 11 (TomEE 7.1.0 Plus and TomEE 8.0.0-M1 microprofile)

Hello, Issue TOMEE-2263 - Copy a war in the webapps folder is not taken into account using Java 11 Issue TOMEE-2264 - Unable to deploy this war on TomEE Plus using Java 11 Could you please look

Re: Johnzon 1.0.1 change in behaviour for final objects

Hi Dave, yes this is tracked in https://issues.apache.org/jira/browse/JOHNZON-142 and 77 long story short setting final fields was not intended and lead to inconsistencies so this behavior has been dropped. if you need the previous behavior and are sure it is intended you can get it back using:

Re: Johnzon 1.0.1 change in behaviour for final objects

Thanks for the explanation Romain. In this case I have been able to remove the final modifiers from the affected fields. This was the simplest thing to do as the mapping was being done automatically in REST API calls rather than explicitly via Johnzon. The problem did take some tracking down. I

Re: Johnzon 1.0.1 change in behaviour for final objects

Failling fast is not really an option since it is the correct behavior and does not violate java contract. We can tune some config like the extsing readAttributeBeforeWrite to reuse it to read your map and enrich it instead of overwriting it but it can also lead to inconsistent values when

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

Here what i has in mind: public class MyClient { private MyClient() { // no-op } public static void main(final String[] args) throws JAXBException { Client client = ClientBuilder.newClient(); try { client.register(new

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

Actually, I just wrote my own MessageBodyReader/writer, annotated it with @Provider, and it is _definitely not_ being invoked while using the JAXRS client. Is that the expected behavior? It *does* work if you call client.register(), but I thought anything annotated @Provider was supposed to be

Re: Heap Memory / boot Tomee

yep, scan.xml controls all the scanning globally for the app Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

Yep, except you instantiate yourself the client outside any container so you are the one to pick it up ;) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: Heap Memory / boot Tomee

OK It seems that tomee only scans my programms as expected except for : -org.apache.openejb.cdi.transactional.MandatoryInterceptor -org.apache.openejb.cdi.transactional.NeverInterceptor -org.apache.openejb.cdi.transactional.NotSupportedInterceptor

Re: Heap Memory / boot Tomee

Hello, it depends the scanning coverage for your app, normally you can tune it using scan.xml (in WEB-INF) to only scan the EE classes (CDI/EJB) and not all others which will reduce it at the minimum. See http://tomee.apache.org/refcard/refcard.html for more details Romain Manni-Bucau

Re: Heap Memory / boot Tomee

Maybe activate -Dopenejb.cdi.debug=true to ensure it is taken into account in your instance Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github |

Re: 2 JIRAs submitted when using Java 11 (TomEE 7.1.0 Plus and TomEE 8.0.0-M1 microprofile)

Thank you for the bug reports! -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

So, currently I'm not instantiating it. I tried both managing it with CDI (@ApplicationScoped AND @Provider), no management (Just annotating @Provider) and it didn't get picked up automatically. The only thing that worked was @ApplicationScoped it and calling client.register on the CDI managed

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

yes Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

So the @Provider annotation does nothing for the jaxrs client essentially. Is this correct? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

Heap Memory / boot Tomee

Hi, I would like to know if increase of heap memory is normal just after booting tomee. I ran GC and analysed hprof in "Memory Analyser" It tells me that I have : - 17,3Mo of "org.apache.bval.cdi.BValExtension". Next ones are -"java.net.URLClassLoader" with 5.1Mo - TomEEWebappClassLoader with

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

Romain Manni-Bucau wrote > You register you provider(s) and cxf should let it be taken cause user > providers are higher priority for the same media type. Got it, so create our own handlers for XML. Romain Manni-Bucau wrote > The messagebody reader/writer are trivial to impl if you have the

Re: Heap Memory / boot Tomee

 just tried using scan.xml but i get: 29-Oct-2018 16:15:16.495 SEVERE [localhost-startStop-1] org.apache.openejb.cdi.OpenEJBLifecycle.startApplication CDI Beans module deployment failed  org.apache.webbeans.exception.WebBeansDeploymentException:

Re: Should the JAX-RS Client pay attention to ContextResolver[s]?

yes Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book