Fixed on trunk. Thanks Juan for pointing the regression.
https://issues.apache.org/jira/browse/TOMEE-1244
Jean-Louis
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com
On Fri, Jun 6, 2014 at 4:02 PM, Romain Manni-Bucau
wrote:
> PS: for the cause: this has been
Hey guys,
We have a regression du to a bad commit. Not really a big deal thought.
The main issue to me is that it has been committed with some other
formatting, finals etc...
Please, make sure to distinguish what is QA (finals, formatting,
checkstyle, PMD, etc) with real code changes.
So that it
PS: for the cause: this has been broken upgrading to quartz 2.2.0 since it
was working with 2.1.x
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-06 15:50 GMT+02:00 R
Hi Juan,
these constructors are useless now. However Patched delegate allows to set
a correct classloader whatever is the other config.
We'll remove them.
Side note: no need to patch the container, you can put the delegate in your
webapp activating TCCL usage.
Romain Manni-Bucau
Twitter: @rm
We are launching Scheduled jobs using the EJB @Schedule feature.
Since we will run on two machines in production, we would like to use a JDBC
Quartz job to make sure the jobs are not run concurrently.
Since our backEnd uses Mysql, we have to use the
"org.quartz.impl.jdbcjobstore.StdJDBCDelegate" dr
Great !
Thanks for the tip.
--
Marian MULLER
SERLI
On Fri, Jun 6, 2014 at 10:04 AM, Romain Manni-Bucau
wrote:
> In pseudo code you can do:
>
> class MyFactory {
>private Properties properties; // + setter
>
>public XXX create() {
> // use properties to build your instance
>
In pseudo code you can do:
class MyFactory {
private Properties properties; // + setter
public XXX create() {
// use properties to build your instance
// properties will match resources properties
}
}
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpr
Hi,
Do you think there is a way to configure queues and topics in tomee.xml
using a property key that contains the destination name ? From what I see,
the property key is used to match a setter or field. Any way to write
configuration like this ?
queues.foo = read=..., write=..., admin=...
queue
