<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>JSR-310 looks useful for defining the current time on the payloads that get fired, which is part of the external API. I think that's about it so far. So considering JSR-310 is alpha, is it still advisable to use that project as part of my API?</div><div><br></div><div>Does anyone else on this list use that project for anything? Please let me know.</div><div><br></div><div>Pete R</div><div><br></div><div><br></div><br><div><div>On 13/05/2011, at 4:58 PM, Jason Porter wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Info is at <a href="http://threeten.sourceforge.net/">http://threeten.sourceforge.net/</a> and apidocs: <a href="http://threeten.sourceforge.net/apidocs/">http://threeten.sourceforge.net/apidocs/</a><div><br></div><div>Just thought it might be a good alternative for the scheduling idea.<br>
<br><div class="gmail_quote">On Fri, May 13, 2011 at 00:51, Pete Royle <span dir="ltr"><<a href="mailto:pete@screamingcoder.com">pete@screamingcoder.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
No. What's it good for?<div><div></div><div class="h5"><br>
<br>
<br>
Jason Porter wrote:
<blockquote type="cite">Maybe a bit of a tangent, but have you thought of using
JSR 310?<br>
<br>
<div class="gmail_quote">On Thu, May 12, 2011 at 18:53, Pete Royle <span dir="ltr"><<a href="mailto:howardmoon@screamingcoder.com" target="_blank">howardmoon@screamingcoder.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">Shane
mentioned Task and Action, of which we both prefer Action.<br>
<br>
I also just thought of Trigger and Notification.<br>
<br>
Pete R<br>
<div>
<div><br>
<br>
George Gastaldi wrote:<br>
> I suggest adding a java.util.concurrent.TimeUnit attribute to
@Every<br>
> annotation and stick to CronEvent naming standard.<br>
><br>
> 2011/5/12 Pete Royle <<a href="mailto:howardmoon@screamingcoder.com" target="_blank">howardmoon@screamingcoder.com</a>>:<br>
><br>
>> Hi All,<br>
>><br>
>> Having trouble deciding on something. Originally observer
methods for<br>
>> scheduled events were quite readable and intuitive, eg:<br>
>><br>
>> public void doStuff(@Observes @Scheduled("10:00") Event e) {
... }<br>
>><br>
>> However, due to possible confusion between
org.jboss.seam.cron.events.Event<br>
>> and javax.enterprise.event.Event Event was renamed to
CronEvent. This is<br>
>> fine, but I wonder if there's any better options. Viable
options I've<br>
>> thought of so far include:<br>
>><br>
>> @Observes @Scheduled("10:00") CronEvent ce<br>
>> @Observes @Scheduled("10:00") Instant i<br>
>> @Observes @Scheduled("10:00") Moment m<br>
>> @Observes @Scheduled("10:00") Tick t<br>
>> @Observes @Scheduled("10:00") Occurrence o<br>
>> @Observes @Scheduled("10:00") Appointment a<br>
>><br>
>> Or maybe go for something different like:<br>
>><br>
>> @Observes @At("10:00") Schedule s<br>
>> @Observes @Recurring("10:00") Schedule s<br>
>><br>
>> I figured since this is going to be the most used part of the
API I would<br>
>> throw it out there for discussion and to see if there are any
better ideas<br>
>> out there.<br>
>><br>
>> It's probably worth mentioining that another part of the API
looks like<br>
>> this:<br>
>><br>
>> @Observes @Every Second s<br>
>> @Observes @Every Minute m<br>
>> @Observes @Every Hour h<br>
>><br>
>> Thanks for the feedback.<br>
>><br>
>> Pete R<br>
>><br>
>> _______________________________________________<br>
>> seam-dev mailing list<br>
>> <a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
>><br>
>><br>
>><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a href="mailto:seam-dev@lists.jboss.org" target="_blank">seam-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Jason Porter<br>
<a href="http://lightguard-jp.blogspot.com/" target="_blank">http://lightguard-jp.blogspot.com</a><br>
<a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>
Software Engineer<br>
Open Source Advocate<br>
Author of Seam Catch - Next Generation Java Exception Handling<br>
<br>
PGP key id: 926CCFF5<br>
PGP key available at: <a href="http://keyserver.net/" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu/" target="_blank">pgp.mit.edu</a><br>
</blockquote>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Jason Porter<br><a href="http://lightguard-jp.blogspot.com/" target="_blank">http://lightguard-jp.blogspot.com</a><br><a href="http://twitter.com/lightguardjp" target="_blank">http://twitter.com/lightguardjp</a><br>
<br>Software Engineer<br>Open Source Advocate<br>Author of Seam Catch - Next Generation Java Exception Handling<br><br>PGP key id: 926CCFF5<br>PGP key available at: <a href="http://keyserver.net/" target="_blank">keyserver.net</a>, <a href="http://pgp.mit.edu/" target="_blank">pgp.mit.edu</a><br>
</div>
</blockquote></div><br></body></html>