Before I start I would like to note that I checked theserverside.com,
java.com but didn't find the answer. I read the Sun's j2ee tutorial
many times. Develop webservice myself.
Ok, here's the simple question:
I need to have a big data structure on the server. It's thread safe.
Then a stateless session allowing client connecting to it. The
stateless session is easy part. My question is where on the J2EE
server that I can put my big data structure that needs initialized
before the server starts, and stay there. It's big and complex that a
simple relational database mapping won't work. I don't want it to be
a record in an entity bean either because it's not that simple. Right
now, I have a corba server running fine with this without any problem.
But I want to migrate to J2EE. I know that I could have this as a
servlet/jsp solution too. My question is with regard to the
enterprise java bean pattern for this. It's just a simple thing on
Corba, and J2EE is natural evolution of the Corba, and I just don't
know what the solution is.
Thank you very much for your time,
Vd.
SMMT - 03 Jun 2004 03:19 GMT
Well, I'm no expert , and I'm only throwing more wood on the fire, but
If you have a already running CORBA app you may have , as a first step make
your J2EE app a simple bridge for CORBA. The client will acess your J2EE App
and the app will acess the already running CORBA App.
For a secound step you may want to implement JCA (Java Connector
Arquitecture). The API's logic is very similar to JDBC's but its exists to
provide acess to more complicated things that a DB , what seam to be your
case.
So a solution is keeping the data were it is and using J2EE as a bridge
first as a CORBA Client , and second via JCA