Hi,
I've been using @Scheduled a lot (great stuff) but I noticed today that only the "cron" attribute of the annotation supports property placeholder configuration since the other two fields are long type.
I couldn't think of any non-ackward solutions to this but I'm trying to set up a @Scheduled with a fixedRate that is defined by a placeholder property. From the looks of it I will have to use the actual Task Scheduling classes to implement this.
Would it be reasonable to have a fixedRateString and fixedDelayString added to @Scheduled so that they could be processed and converted into long's by the container or is this a bad way to add features to an annotation?
Thanks.


Reply With Quote