Re: Change the location of tomee.xml

If you need global JTA resources then there they should get managed on the container level. This is a clean separation of concerns. The app says „I need resource X“ and the whole configuration and setup is done on container level depending on the system. Different stages or even customers

Re: Calling separate EJB from Web project deployed on same server

If not in the same application it is the easiest yes because arguments will be copied between classloaders to allow you to provide the same API in both webapps. If your bean is not remote then it is avoided IIRC but parameters need to be shared. Romain Manni-Bucau @rmannibucau

Re: Change the location of tomee.xml

2016-02-12 10:00 GMT+01:00 Mark Struberg : > > If you need global JTA resources then there they should get managed on the > container level. This is a clean separation of concerns. The app says „I > need resource X“ and the whole configuration and setup is done on container >

Re: rest exceptionmapper in ear

Always my pleasure :-) java.lang.ClassNotFoundException: whatever.provider.SmartGuestExceptionMapper at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1722) ~[catalina.jar:7.0.63] at

Re: rest exceptionmapper in ear

I see two things in this stack: - it is using the webapp loader so sounds ok - it is done in the RESTService so the right moment If you can debug this last one maybe you can sort it out, wonder if we can use the wrong webapp due to scanning? Would be unlikely but that's the only cause I can

rest exceptionmapper in ear

Hi just one observation: tomee 1.7.3 I've got an ear with several wars etc. 1. adding custom exceptionmappers to one of the wars 2. default system properties 3. WEB-INF/openejb-jar.xml may or may not include mappers definition => a lot of: WARN OpenEJB.rs - can't load

Re: Calling separate EJB from Web project deployed on same server

Thank you Romain The global lookup is working. When using either the global or LocalInitialContextFactory must one always send serializable data types as parameters? It is running on the same TomEE server so in the same JVM. /Caused by: java.io.NotSerializableException:

Re: rest exceptionmapper in ear

Hepp, I'll give it a shot. 1. The only thing I can verify right now is that it seems that the @providers are initalized on all wars. I did remove al the other wars and the exceptions went away. 2. put my mappers in a separate lib into ear/lib: 2.1 openejb-jar has mapper references,