All of the examples for EJB's I've seen involve some sort of e-commerce. I have a situation that is not e-commerce but looks like it might be a good candidate for using EJB's. I hope anyone with J2EE and EJB experience can let me know whether I am on the right track.
We are designing a system that will serve as sort of a master for other systems in the network. It will have a database, but we want to mask the details of the database from the rest of the system as much as possible. The other systems will need controlled access to the database, and all information passing over the network needs to be encrypted. We would like to have information added to the database initiate an action on one of the other systems, but I don't know of way to use EJB to do that.
What do you think? Is EJB overkill, or the wrong solution altogether? Or am I on the right track? I've played around with EJB but never used them on a large scale system.
I am Arthur, King of the Britons. And this is a tiny ad:
the new thread boost feature: great for the advertiser and smooth for the coderanch user