Ruslan Sibgatullin 31d634e6bf Added cron expression validation method for CronSequenceGenerator ...

It's handy to know in advance whether or not expression that is
passed to CronSequenceGenerator or CronTrigger constructor would
not results in IllegalArgumentException. The only way to do it
now is to try\catch an instance creation but it's kinda ugly.

2016-04-23 17:56:29 +03:00

..

aop

Remove duplicate words

2016-04-19 08:24:21 +02:00

beans/factory

Ignored test removed (not intended to work)

2016-03-23 18:15:29 +01:00

cache

Polishing

2016-04-13 13:56:37 +02:00

context

Manage asynchronous EventListener with replies

2016-04-15 13:22:11 +02:00

core/task

Update Apache license headers for affected sources

2012-12-28 23:09:31 +01:00

ejb

Harmonize resources location

2015-02-28 10:32:40 +01:00

format

Consistently strict parsing of date overflows (using java.time's strict resolution style)

2016-02-23 16:12:26 +01:00

instrument/classloading

Harmonize resources location

2015-02-28 10:32:40 +01:00

jmx

Polishing

2016-04-11 21:20:31 +02:00

jndi

Consistent formatting of license headers, package javadocs, and import declarations

2014-10-21 01:44:07 +02:00

mock/env

Remove duplicate test classes

2013-01-04 10:02:29 +01:00

remoting

Consistent formatting

2016-03-24 19:22:50 +01:00

scheduling

Added cron expression validation method for CronSequenceGenerator

2016-04-23 17:56:29 +03:00

scripting

Consistent formatting

2016-03-24 19:22:50 +01:00

tests

Consistent formatting of license headers, package javadocs, and import declarations

2014-10-21 01:44:07 +02:00

ui

Add @Override to remaining source files

2013-05-13 17:04:56 -05:00

util

Consistent formatting of license headers, package javadocs, and import declarations

2014-10-21 01:44:07 +02:00

validation

DataBinder test for java.util.Optional property

2016-02-19 19:21:09 +01:00