AW: [jbpm-dev] Re: jBPM 4 limitations
Hi!
A short comment on JMS and EJB Timers: Currently you can either use both
or none. And since EJB Timers fail to scale well, in the bigger projects I
know we always used the JobExecutor and skipped JMS and EJB Timers. And
the JobExecutor scales perfectly well, so this is not a problem in my
eyes. Maybe to not have the JMS Marketing sticker is not that good, but
this is for you to judge...
Cheers
Bernd
-----Ursprüngliche Nachricht-----
Von: jbpm-dev-bounces(a)lists.jboss.org
[mailto:jbpm-dev-bounces@lists.jboss.org] Im Auftrag von Tom Baeyens
Gesendet: Montag, 11. Mai 2009 11:04
An: Burr Sutter
Cc: Len DiMaggio; jBPM Dev List; Mark Little; John Graham
Betreff: [jbpm-dev] Re: jBPM 4 limitations
>>> * no async messaging through JMS
> That will make some jBPM3 users unhappy. NTT feels this will add
> scalability, especially in a cluster.
Same here. We have all functional components in place, but except for
QA. Setting
that up requires productization resources which we don't
have. So that work is now serialized and will have to be > > prioritized
after GA.
>> * no timer support through EJB Timer