Hi!
"Keith L. Musser" wrote:
> Are you saying creating an MLET entry in the jboss.conf will be portable
> to other EJB servers?
No, to other JMX servers. Some EJB servers support JMX today, and some
can easily be extended to do so. Basically, if your server allow you to
add "startup classes", then you can add your own startup class which
creates a JMX MBeanServer and registers your portable JMX MBean. If it
doesn't allow you to add custom code, then it's a crappy server and
should be avoided anyway ;-)
> I don't think that's what you're saying, but I'm
> not sure what your point is about JMX.
That it's portable between JMX compliant servers. Eventually all J2EE
servers will be JMX compliant.
> My point is that I am stuck making a long-lived client which calls my
> beans periodically, and that means that I can't put the whole thing in
> my ejb.jar file. Which means it's not portable.
Well, one thing I hadn't considered before, but would give you
J2EE-portable long-lived clients is to make a servlet that create this
thread in initConfig(). That should work too, and it will only use
J2EE-API's.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
