[
https://issues.jboss.org/browse/SEAMCRON-28?page=com.atlassian.jira.plugi...
]
Martin Kouba commented on SEAMCRON-28:
--------------------------------------
I think it would be better to allow module user to utilize full configuration abilities of
underlying implementation (quartz, queuj, ...). Exposing common settings will result in
reducing those possibilities. Nevertheless either of these is much better than hard-coded
configuration :-).
Make settings like ThreadPool configurable
------------------------------------------
Key: SEAMCRON-28
URL:
https://issues.jboss.org/browse/SEAMCRON-28
Project: Seam Cron
Issue Type: Enhancement
Affects Versions: 3.0.0.Alpha1
Reporter: Peter Royle
Assignee: Peter Royle
Labels: configuration, per, provider
Fix For: 3.0.0.Alpha2
The main dilemar here is whether or not we should expose common settings in the API so
that users need only learn one syntax, or should the provider provide the config options
so only those options supported by the provider are accessible when using that provider?
Not all options will be supported by all providers and vice versa.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira