Perhaps I was confused: you mentioned MBean, is this shorthand for message
bean or something to do with JMX?
I agree using proprietary features isn't great, but when used with caution
there is no reason to not use them.
Myles
> -----Original Message-----
> From: Rickard �berg [SMTP:[EMAIL PROTECTED]]
> Sent: 30 November 2000 08:59
> To: [EMAIL PROTECTED]
> Subject: Re: How to do async processing in EJB?
>
> Hey
>
> "Jeffery, Myles" wrote:
> > Message beans is part of the EJB 2.0 specification.
>
> And what does Message Beans have to do with this?
>
> > An alternative solution is to use a propietary WebLogic feature: startup
> > classes.
> >
> > With startup classes you can create as many threads as you like. They
> can
> > subscribe to WebLogic's timer service to create the timing notifications
> you
> > desire. When a notification occurs your thread can then call one of
> your
> > session beans.
>
> Properietary sucks. Period.
>
> If WL doesn't support plugging in custom MBeans yet I would suggest
> doing a WL startup class that simply creates a MBeanServer and then
> registers your nice portable MBeans in that. Much better.
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
>
> ==========================================================================
> =
> 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".
