<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ok, thanks for advice <span class="moz-smiley-s1"><span> :-) </span></span>.
I explored Seam Cron JIRA and made some comments and tickets.<br>
<br>
Martin<br>
<br>
Dne 8.8.2011 19:17, Jason Porter napsal(a):
<blockquote
cite="mid:CAF9TksMWudACkK5dmH2Pe7N9RndBKZW2w78yCEcgg3UUc1=3Ng@mail.gmail.com"
type="cite">Thanks for the ideas. I know Peter has been very busy
over the past few weeks with his normal job. My advice would be to
create JIRA tickets if they don't exist and start issuing pull
requests to help us out :)<br>
<br>
<div class="gmail_quote">2011/8/8 Martin Kouba <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:mkouba@redhat.com">mkouba@redhat.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> <font
face="sans-serif">Hi!<br>
<br>
Recently I tested Seam Cron module, especially scheduling
features. From my point of view Seam Cron module (as well
as Seam 2) is still not usable for quite common scheduling
scenarios. Below are some
comments/observations/suggestions - most of them come from
real app needs and are closely related to quartz because I
used this lib in many JEE apps before.</font><font
face="sans-serif"><br>
<br>
In any case I don't want to criticize but make Seam 3 more
useful <span><span> :-) </span></span>!</font> If needed
I can offer some help.<br>
<font face="sans-serif"><br>
* <b>Seam Cron has fixed quartz configuration</b> (no way
to change it); this is not a good idea and will surely
limit module user (QUARTZ -
org.jboss.seam.cron.scheduling.quartz.QuartzScheduleProvider)<br>
* <b>I'm missing operations on scheduler</b>; e.g. send
event to pause or resume all jobs (API)<br>
* <b>job observers "may be/and may inject" @Dependant or
@ApplicationScoped beans only</b>; sometimes its very
useful to reuse request scoped components - e.g. inject
service used also from GUI (API/QUARTZ, in weld/quartz
this could be accomplished with org.quartz.JobListener and
org.jboss.weld.context.bound.BoundRequestContext)<br>
* <b>it's not possible to schedule jobs dynamically</b> -
for instance first get definitions (DB, XML, WS) and then
schedule them (API, maybe schedule job by firing some
special event)<br>
* <b>fired jobs are always stateless</b>; sometimes its
very practical to have stateful jobs / implement
org.quartz.StatefulJob (API, QUARTZ -
org.jboss.seam.cron.scheduling.quartz.TriggerJob
implements org.quartz.Job)<br>
* <b>trigger may contain next fire time info</b> -
sometimes very practical to know (API -
org.jboss.seam.cron.api.scheduling.Trigger)<br>
* <b>finally is there a reason not to use new stable
versions of quartz, e.g. 1.8.x or 2.0.x</b>? <br>
<br>
Martin</font><font face="sans-serif"><br>
</font><font color="#888888">
<pre cols="72">--
Martin Kouba
JBoss Quality Assurance Engineer
E-mail: <a moz-do-not-send="true" href="mailto:mkouba@redhat.com" target="_blank">mkouba@redhat.com</a>
Web: <a moz-do-not-send="true" href="http://www.cz.redhat.com" target="_blank">www.cz.redhat.com</a>
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic</pre>
</font></div>
<br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Jason Porter<br>
<a moz-do-not-send="true" href="http://lightguard-jp.blogspot.com"
target="_blank">http://lightguard-jp.blogspot.com</a><br>
<a moz-do-not-send="true" 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 moz-do-not-send="true"
href="http://keyserver.net" target="_blank">keyserver.net</a>, <a
moz-do-not-send="true" href="http://pgp.mit.edu" target="_blank">pgp.mit.edu</a><br>
</blockquote>
<br>
</body>
</html>