Agenda for 2011-05-18 21:00 UTC
by Jason Porter
- Good news: Brian Leathem joining Red Hat
- Community Integrator
- Seam Reports underway
- Seam Spotlight volunteer(s)
- Module page updates
- Seam 3 forums - leads please subscribe to RSS /
seam-forums(a)lists.jboss.org
- Recap of git workflow actual usage
- Cloudbees trial
- Compatibility module / migration
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
14 years, 12 months
WELD-862 and Seam Cron
by Peter Royle
Hi,
I'm aiming to make a release of Seam Cron available within the next two weeks. Currently there is an outstanding issue (https://issues.jboss.org/browse/WELD-862) which prevents Cron from running properly with Weld. I have been able to carry on developing Cron by testing it against OpenWebBeans, but obviously if we are to release a Seam module it should work against Weld.
It would be nice if WELD-862 could be fixed as soon a possible so that all future versions will work well with Cron.
But more importantly I also probably need to do something special in Cron so that it will work with the version of Weld already deployed in JBoss AS and Glassfish, which will contain the bug. The workaround mentioned in the bug report is to deep copy the InvocationContext. I attempted to do this by serialising and unserialising the InvocationContext but couldn't due to UnserializableExceptions. Does anyone have any advice for me about how I might be able to work around this bug to support existing versions of Weld?
Cheers,
Pete R
15 years
Seam Cron API
by Cloves Almeida
Sorry, I meant Pete.
Em 13-05-2011 05:36, seam-dev-request(a)lists.jboss.org escreveu:
> Seam Cron API
15 years
Seam social API stabilisation is near.
by Antoine Sabot-Durand
Hi Team,
After some pain, suffering and knots in my brain, I found a clean answer to my multi-account issue (thanks to dependent scope, @Any qualifier and Instance<> class).
I created a qualifier to distinguish different services beans in a polymorphic context. The purpose of this qualifier is only to bind some beans (settings, controller) to a given social service. To be as generic as possible it takes a binding (in opposition to @Nonbinding) parameter which is an enum related to service name. So @RelatedTo(Service.Twitter) qualifies a bean in relation to Twitter. I'm not very happy with this name "RelatedTo" but didn't found something short and eloquent (I avoided @InRelationTo :-) ). Suggestion and commentaries are welcome. (the source is in multi_account feature branch)
thxs
Antoine SABOT-DURAND
15 years
Seam Cron API
by Cloves Almeida
Peter,
there's also the issue of whether Request and Session context should be
available during job processing.
15 years
Seam Reports
by George Gastaldi
Hello !
I started some work on Seam Reports, but I would like some help from
you guys. I created some interfaces to abstract loading/compiling a
report, populating and rendering.
The source code is on https://github.com/gastaldi/reports (not merged
on official repos yet) - test case included (and passing) !.
I recommend read the api and impl code before.
But the points I am in need of help are:
1) The rendering part is kinda obscure yet. It would be nice if the
developer could write something like:
@Inject @PDF SeamReportRenderer renderer;
and then call renderer.render(...);
The fact is that: Every provider (JasperReports, Velocity, Birt, etc)
have their own way of doing the rendering part.
I created a SeamReportsOutputType enum, but that is not so cool, as
will certainly restrict the app developer. Jason Porter and Pete Royle
has pointed me that using Qualifiers (as the example above) should be
a good way to go.
2) Should the interfaces be rich enough to allow someone to create a
report by using a fluent interface (I believe that could be out of
scope of this module) or this module should just allow hiding the
implementation layer of existing reports framework as it does now (In
my iniitial conception, this is what I needed and wanted) ?
I´ll love to hear your suggestions,
Regards,
George Gastaldi
15 years
Seam Cron API
by Cloves Almeida
Peter,
there's also the issue of whether Request and Session context should be
available during job processing.
15 years
Re: [seam-dev] Seam Cron API for scheduled .... things
by Peter Royle
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?
Does anyone else on this list use that project for anything? Please let me know.
Pete R
On 13/05/2011, at 4:58 PM, Jason Porter wrote:
> Info is at http://threeten.sourceforge.net/ and apidocs: http://threeten.sourceforge.net/apidocs/
>
> Just thought it might be a good alternative for the scheduling idea.
>
> On Fri, May 13, 2011 at 00:51, Pete Royle <pete(a)screamingcoder.com> wrote:
> No. What's it good for?
>
>
>
> Jason Porter wrote:
>>
>> Maybe a bit of a tangent, but have you thought of using JSR 310?
>>
>> On Thu, May 12, 2011 at 18:53, Pete Royle <howardmoon(a)screamingcoder.com> wrote:
>> Shane mentioned Task and Action, of which we both prefer Action.
>>
>> I also just thought of Trigger and Notification.
>>
>> Pete R
>>
>>
>> George Gastaldi wrote:
>> > I suggest adding a java.util.concurrent.TimeUnit attribute to @Every
>> > annotation and stick to CronEvent naming standard.
>> >
>> > 2011/5/12 Pete Royle <howardmoon(a)screamingcoder.com>:
>> >
>> >> Hi All,
>> >>
>> >> Having trouble deciding on something. Originally observer methods for
>> >> scheduled events were quite readable and intuitive, eg:
>> >>
>> >> public void doStuff(@Observes @Scheduled("10:00") Event e) { ... }
>> >>
>> >> However, due to possible confusion between org.jboss.seam.cron.events.Event
>> >> and javax.enterprise.event.Event Event was renamed to CronEvent. This is
>> >> fine, but I wonder if there's any better options. Viable options I've
>> >> thought of so far include:
>> >>
>> >> @Observes @Scheduled("10:00") CronEvent ce
>> >> @Observes @Scheduled("10:00") Instant i
>> >> @Observes @Scheduled("10:00") Moment m
>> >> @Observes @Scheduled("10:00") Tick t
>> >> @Observes @Scheduled("10:00") Occurrence o
>> >> @Observes @Scheduled("10:00") Appointment a
>> >>
>> >> Or maybe go for something different like:
>> >>
>> >> @Observes @At("10:00") Schedule s
>> >> @Observes @Recurring("10:00") Schedule s
>> >>
>> >> I figured since this is going to be the most used part of the API I would
>> >> throw it out there for discussion and to see if there are any better ideas
>> >> out there.
>> >>
>> >> It's probably worth mentioining that another part of the API looks like
>> >> this:
>> >>
>> >> @Observes @Every Second s
>> >> @Observes @Every Minute m
>> >> @Observes @Every Hour h
>> >>
>> >> Thanks for the feedback.
>> >>
>> >> Pete R
>> >>
>> >> _______________________________________________
>> >> seam-dev mailing list
>> >> seam-dev(a)lists.jboss.org
>> >> https://lists.jboss.org/mailman/listinfo/seam-dev
>> >>
>> >>
>> >>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>>
>> --
>> Jason Porter
>> http://lightguard-jp.blogspot.com
>> http://twitter.com/lightguardjp
>>
>> Software Engineer
>> Open Source Advocate
>> Author of Seam Catch - Next Generation Java Exception Handling
>>
>> PGP key id: 926CCFF5
>> PGP key available at: keyserver.net, pgp.mit.edu
>
>
>
> --
> Jason Porter
> http://lightguard-jp.blogspot.com
> http://twitter.com/lightguardjp
>
> Software Engineer
> Open Source Advocate
> Author of Seam Catch - Next Generation Java Exception Handling
>
> PGP key id: 926CCFF5
> PGP key available at: keyserver.net, pgp.mit.edu
15 years
Seam Cron API for scheduled .... things
by Pete Royle
Hi All,
Having trouble deciding on something. Originally observer methods for
scheduled events were quite readable and intuitive, eg:
public void doStuff(@Observes @Scheduled("10:00") Event e) { ... }
However, due to possible confusion between
org.jboss.seam.cron.events.Event and javax.enterprise.event.Event Event
was renamed to CronEvent. This is fine, but I wonder if there's any
better options. Viable options I've thought of so far include:
@Observes @Scheduled("10:00") CronEvent ce
@Observes @Scheduled("10:00") Instant i
@Observes @Scheduled("10:00") Moment m
@Observes @Scheduled("10:00") Tick t
@Observes @Scheduled("10:00") Occurrence o
@Observes @Scheduled("10:00") Appointment a
Or maybe go for something different like:
@Observes @At("10:00") Schedule s
@Observes @Recurring("10:00") Schedule s
I figured since this is going to be the most used part of the API I
would throw it out there for discussion and to see if there are any
better ideas out there.
It's probably worth mentioining that another part of the API looks like
this:
@Observes @Every Second s
@Observes @Every Minute m
@Observes @Every Hour h
Thanks for the feedback.
Pete R
15 years
