This week's book giveaway is in the Testing forum. We're giving away four copies of The Way of the Web Tester: A Beginner's Guide to Automating Tests and have Jonathan Rasmusson on-line! See this thread for details.
My problem at the moment is that I can't get my MBean to access a session bean.
I've tried a few things with both local and remote and nothing worked yet, google hasn't produced success either.
But before I waste anymore time on this, unless of course you know how to do that, I wonder if
I shouldn't go back to solving the original problem with something else.
In a nutshell, I have some work that should be done every once in a while, check db, process records,
make web service requests etc.
This process should be manageable, the client or rather operations team wants to be able to stop and start it,
and maybe even increase the number of workers.
Now I thought of MDBs, the MBean could kick off as many MDBs as the client requests but you can't stop an MDB,
now maybe here is where you can suggest an alternate. If the client wants to stop processing and the MDB is busy I don't
know how to stop it, I thought of boolean type thing controlled someplace that the MDB checks, but we're in a cluster and static variables
could wind up different in each JVM.
I then got going on a Timer EJB that the MBean holds a reference to, a collection of them so it can cancel them when the user
wants to decrease or stop them all entirely.
This is my current problem, I'd love any ideas especially if they lead to a new problem