thanks, david
this was my guess for creating background processes at the moment i have
read this topic the first time...now i know, i am on the right highway
with my async native communication with semi-active outside mbean
services.
:)))
bax
Am Mit, 2002-03-06 um 17.29 schrieb David Jencks:
> U
, March 06, 2002 5:30 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Background process
Use an mbean extending ServiceMBeanSupport, and start the thread in
startService. If the requirement on code location is really a _requirement_
use jboss 3 and put the mbean code + config in a .sar in your .ear
Use an mbean extending ServiceMBeanSupport, and start the thread in
startService. If the requirement on code location is really a _requirement_
use jboss 3 and put the mbean code + config in a .sar in your .ear. You may
need to have the mbean "depends" on the ejbs it uses so it waits to start
unti
ee if you need more assistance =)
Good Luck!!
Tim.
- Original Message -
From: "Loïc Lefèvre" <[EMAIL PROTECTED]>
To: "JBoss User Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, March 06, 2002 4:22 PM
Subject: RE: [JBoss-user] Background process
> Firs
ne-
De : Tim Yates [mailto:[EMAIL PROTECTED]]
Envoyé : mercredi 6 mars 2002 17:04
À : Loïc Lefèvre
Objet : Re: [JBoss-user] Background process
How about a MessageDriven Bean (MDB)?
Or I believe there is a Timer bean, which you can get to call your bean at
regular intervals...
Tim.
---
Hi,
Could someone tell me the best way to implement a background
process (a thread) that has access to some EJBs (server side).
The code of this process must be in the ear archive.
Currently, I have only two ideas:
- Run my thread in the init method of a servlet.
- Run my thread in a static block
