Hugo Pragt wrote on Apr 13, 2008 05:59 PM:
That for a start is wrong, you can only choose one dispatcher.
No, no exceptions at all. That is what I find the most scary actually.
I'll try to remove the <core:dispatcher/> from components.xml and test again.
My current guess is that the call quietly dies on some exception which I do not log.
Nothing to do with the Timer injection except that it triggers the exception.
what scope is the timer?
you cant inject session scoped components!
What version of Seam are you using, and which dispatcher? timer / quartz / ejb?
IIRC in one version of Seam, async exceptions were swallowed.
Since the last time, I updated my Seam version.
I should check if I can still reproduce this case.
timers come from the jboss timer-service-dispatcher.
About the scope of the timer: I understood that a Timer object is outjected by seam when doing an asynchronous call. I do not know the scope of this object but I assume
(yes I know what assumptions are ...)