Re: 7.0.4 context reload affects resource

2017-10-11 Thread Andy Gumbrecht
Hi Matthew, The users list is not the ideal place to post stacktraces or bugs. Can you please file this in a JIRA ticket so we can track it better here: https://issues.apache.org/jira/projects/TOMEE Thanks, Andy. On 11/10/17 03:36, Matthew Broadhead wrote: hi, in

Re: Diff between TomEE Plus 7.0.3 and 7.0.4

2017-10-11 Thread Andy Gumbrecht
Hi Francois, The 7.0.4 version is available as you have already seen, but the official announcement has not yet been made - I will link the release notes and blog post and send out the information in the next few days. Andy. On 11/10/17 01:28, COURTAULT Francois wrote: Hello everyone,

Re: TomEE 7.0.2 and Shiro 1.4.0 - commons-beanutils error

2017-10-11 Thread Romain Manni-Bucau
We didnt need to upgrade so we didnt do but we can also remive the container only loading of the lib and load it from the app if better on the long run. Le 11 oct. 2017 13:37, "gilbertoca" a écrit : > Romain Manni-Bucau wrote > > Not sure what you mean bit you can fix it

Re: TomEE 7.0.2 and Shiro 1.4.0 - commons-beanutils error

2017-10-11 Thread gilbertoca
Romain Manni-Bucau wrote > Not sure what you mean bit you can fix it in your project - what is what I > meant ;). I know, Romain! I've posted the solution of the problem [1] back in June. I'm trying to help reporting that the problem persists (was erroneously?). [1]

7.0.4 context reload affects resource

2017-10-11 Thread Matthew Broadhead
hi, in src/main/webapp/META-INF/context.xml i have defined         mail.smtp.port="465" mail.smtp.auth="true" mail.smtp.user="u...@domain.tld"         mail.smtp.password="password" password="password"         mail.transport.protocol="smtp" mail.smtp.ssl.enable="true" /> it worked fine in 7.0.3

Re: Diff between TomEE Plus 7.0.3 and 7.0.4

2017-10-11 Thread Romain Manni-Bucau
Hi François, johnzon 1.1 is java 8, tomee 7 must stick to java 7 Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-11 10:28 GMT+02:00 COURTAULT Francois : > Hello everyone, > > First, is there any doc somewhere describing the changes

Diff between TomEE Plus 7.0.3 and 7.0.4

2017-10-11 Thread COURTAULT Francois
Hello everyone, First, is there any doc somewhere describing the changes between TomEE 7.0.3 and 7.0.4 ? I have looked at the main differences between the two versions: * Tomcat 8.5.20 in TomEE 7.0.4 instead of 8.5.11 in TomEE 7.0.3 * ActiveMQ 5.14.5 in TomEE 7.0.4 (previous

Re: DefaultManagedExecutorService lookup in JNDI

2017-10-11 Thread Romain Manni-Bucau
It defines the link only, which means it does the same as your @Resource. Difference is that if you don't have any @Resource then it would still do it if true by default. Then if there is a link and no matching resource then openejb creates one implicitly. This means that false is a good default

Re: DefaultManagedExecutorService lookup in JNDI

2017-10-11 Thread Paul Carter-Brown
Thanks Romain/Andy, openejb.environment.default = true fixed it Does this property merely indicate that the resources should be bound into the JNDI tree or does it control whether they are created or not by the container? I found it interesting that this works fine even with that property set

Re: TomEE 7.0.2 and Shiro 1.4.0 - commons-beanutils error

2017-10-11 Thread Romain Manni-Bucau
Not sure what you mean bit you can fix it in your project - what is what I meant ;). Le 11 oct. 2017 01:04, "gilbertoca" a écrit : > The pom.xml from github(apache/tomee): > > tomee > https://github.com/apache/tomee/blob/acacacee9b1ae52bc2373f69242924 >