@kenglover: Thanks, but i'm using Quartz not EJB-Timers. I'm sorry, should have
told it.
@pete.muir: I tried the approach by scheduling an asynchronous task at startup,
which performs some operations and gives the control for the next operation to
a new asynchronous task. This works fine for
Have you got the idea what i'm doing ? Is jBPM an option for doing this ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090287#4090287
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4090287
My suggestion was to use an @Asynchronous method which schedules another
@Asynchronous method when it completes.
No, don't know what you are trying to do as you've never explained that.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090288#4090288
Reply to
I tried to explain it by posting pseudo-code ...
I like to create a simple service which runs in it's own thread from startup of
seam until shutdown. The service itselve performs synchron tasks ..
Hmm. How could i explain it better ?
View the original post :
No, you're still explaining how you want to solve your problem, not what your
problem is.
Your solution is definitely an anti-pattern when used with Seam.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4090325#4090325
Reply to the post :
Maybe this will help...
I needed to schedule a regular recurring job from startup to shutdown. This
job polls out LDAP servers and keeps a list of the ones that are up.
There are 2 components, a controller, and the asynchronous job. The controller
runs at startup and schedules the job,
If i start an Asynchronous method with an IntervalDuration assigned, the
interval will be timed from the last 'start' of the method not from the the
last execution-end.
This causes the Tasks to be launched in parallel if the previous task was not
finished because it needs longer than the
So, if we fix the bug with not being able to schedule an async inside an async
call, then you can do that right?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4088867#4088867
Reply to the post :
No, i don't think so ...
I need something like the following
PseudoCode:
| @Stateful
| @Startup
| @Name(batch)
| @Scope (ScopeType.APPLICATION)
| @TransactionManagement (TransactionManagementType.BEAN)
| public class BatchBean implements Batch {
|
| private AtomicBoolean
the @Asynchronous inside the @Asynchronous - topic is needed for another task
in my application ...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4088964#4088964
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088964
I don't understand why @Asynchronous doesn't work for you?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4088461#4088461
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088461
___
Is there a way to ask seam, whether is is started up ?
I tried to create an MBean which spawn's a thread doing the recurring job.
But MBeans are initialized before Seam is up in JBoss ...
Any ideas ?
View the original post :
12 matches
Mail list logo
