I agree with the need for a conceptual envelope - as I stated in a previous
post, I used HP OpenView in a previous project. I don't like the use of
Startup classes particularly as they are not manipulable/restartable etc -
but they do (partly) solve this need.
My understanding is that a JMX server (MBeanServer?) should be able to
provide that functionality - and that 'System Controllers' (I can't think
what other term to use) are/will be available. These will also look after
the AppServer, as well as any other applications/beans/executables/loggers.
tim
> -----Original Message-----
> From: Rich Johns [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, June 20, 2000 3:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Logging in Enterprise Applications
>
> Rickard �berg wrote:
>
> > <snip>good info </snip>
> >
> > That's my take on it. If your particular server does not yet support
> > JMX, at least it might support "startup classes" to allow you to extend
> > it, and you could use that to start your own JMX MBeanServer to register
> > these portable JMX components.
> >
>
> Something may have just clicked. It was faint though. If I use a startup
> class
> to launch an rmi object and bind it to JNDI such that ejbeans can access
> and
> use it, are you saying that I might just as well be using a JMX
> MBeanServer?
>
> I see the startup class as a way to extend the app server but also as a
> way
> to start up a resource provider (that is threaded) and be legal wrt to the
> spec's
> law against ejbeans starting threads. It also makes it unecessary to
> launch
> a stand alone app to get resources started that are not provided by the
> appserver. Not sure if this is a broken idea. One problem though, is how
> to
> know when to shut down the rmi object (release it's resources, etc.)
>
> What advantages does a JMX server have over just launching the rmi object?
> Portablbility maybe? although you still need to use the "startup class"
> (at
> least for
> now) to get it going.
>
> I've been struggling against this need that seems to keep popping up for
> some sort of conceptual envelope surrounding the appserver -- this
> envelope
> does things like starts rmi objects, put's things in JNDI, etc. The
> tendancy is
> to try and solve all these managment and initialization needs in terms of
> the appserver container and stateless beans and various other contortions.
> Maybe this conceptual envelpe is JMX. Anyway, that was the faint click.
> Did I really hear it?
>
> > /Rickard
> >
> > --
> > Rickard �berg
> >
> > @home: +46 13 177937
> > Email: [EMAIL PROTECTED]
> > http://www.telkel.com
> > http://www.jboss.org
> > http://www.dreambean.com
> >
> >
> ==========================================================================
> =
> > 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".
This e-mail, and any attachment, is confidential. If you have received it in error,
please delete it from your system, do not use or disclose the information in any way,
and notify me immediately. The contents of this message may contain personal views
which are not the views of the BBC, unless specifically stated.
===========================================================================
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".
