The specification doesn't really provide for this to my knowledge.
However I suspect most implementations provide for an "initialization"
engine which could start an object running for you. GemStone/J has such a
capability, and I am pretty sure WL does too.
This object would not be a Session or Entity bean though. It would just be
an "agent" object that lives in a thread. This agent would be a client to
your beans. Make sense?
Regards,
-Chris.
> -----Original Message-----
> From: Ronseaux Cyril [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, May 05, 2000 11:25 AM
> To: [EMAIL PROTECTED]
> Subject: Background tasks Bean
>
> I would like to have a bean always running, performing tests on my server,
> running rule engine, peering into my mailbox, etc.
> I would like to make a bean which run from my server startup without
> stopping.
>
> well, my bean will be a session bean, singleton if possible.. oh BTW how
> do
> you do singleton beans ?
>
> Any pointer ?
>
> tia, regards,
> Cyril
>
> ==========================================================================
> =
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
