"jamesstrachan" wrote : Let's start with the timer, as that's simple.
|
| ...
|
| That gives you a trigger that works, and can be adjusted to reload as frequently
as you require.
|
from where would you call this code tho ? If you do it from onMessage it might not be
called for a lon
Ok, here's an idea ;)
-I set up a java preferences listener from an InitServlet.
-The listenere gets destroyed along with the servlet, so it won't hang around after an
undeploy.
-The listener will hava a constructor that looks up an ejb with lookup/home/narrow
etc. , plain client ejb lookup.
-Th
hmm, been pondering more ^_^
I think I know better what I want now.
let's say we want a MDB that puts received messages in a database, I use a 3'd party
db binding so I'm not using entity beans.
I want a jdbc connection for this, I want to share it between the MDB's, and I want it
to be changea
Thanks for the input :)
Looks like an option, but it doesn't make me very happy, especially the fact that I
have to wait (possibly long) for the configuration change to have any effect (I'd like
it to be soon, cause thisway it's possible to notice configuration mistakes).
you mention using a ti
Btw. JMX seems to be what I've after, and I've considered using it a lot, but with JMX
I have some problems:
- JMX does not ofer persistence by itself
- Which means I'd have to write my own jmx persistence, which seems a task that'd be
too great for this project.
- Even if I would there's the pro
Right, lessee if I can explain my problem :)
- I'm building a server application including Message Driven Beans.
- These Beans have settings such as url's to retrieve things from.
- These settings need to be changable in runtime via a servlet/www interface.
- I'd like to use a generic preferences/
