[
https://issues.apache.org/jira/browse/DELTASPIKE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156138#comment-15156138
]
Gerhard Petracek edited comment on DELTASPIKE-1081 at 2/21/16 6:26 PM:
-----------------------------------------------------------------------
the current format is:
{code}
@Scheduled(cronExpression="{myConfigKey}")
{code}
with that we don't have to validate cronExpression vs externalCronExpression
and we still follow the notion of keys (like in other areas of ds as well as
specs. like bean-validation).
was (Author: gpetracek):
the current format is: @Scheduled(cronExpression="{myConfigKey}")
with that we don't have to validate cronExpression vs externalCronExpression
and we still follow the notion of keys (like in other areas of ds as well as
specs. like bean-validation).
> Offer the possibility to provide the cron expression via configuration
> ----------------------------------------------------------------------
>
> Key: DELTASPIKE-1081
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1081
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Scheduler
> Reporter: Pablo Pita Leira
> Assignee: Gerhard Petracek
> Priority: Minor
> Attachments: DELTASPIKE_1081_draft.patch
>
>
> Currently the cron expression used when scheduling jobs should be hardcoded
> within the @Scheduled annotation.
> It would be nice to offer the users the possibility to provide the cron
> expression via external configuration.
> @Scheduled(externalCronExpression="my.expression")
> The property my.expression would be provided by DeltaSpike's ConfigResolver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
