Hi,
I'm working on the high level architecture of a port from Corba
services to an EJB+Corba appserver, mainly to get the modern management
and controls that current servers have.
Some of our services are simple stateless Corba services that could be
re-packaged, with work, into stateless session beans. But why, they
don't use OTS now and won't ever, so why port to EJB SB's?
Most Corba+EJB server vendors offer DB connection pooling to the Corba
services just like EJB so no gain there.
Given how corba method calls can be dispatched to re-entrant single
objects on the server and the EJB container must create a unique object
per SB method call, or pool a finite number, seems there's a memory and
performance gain with Corba.
Admittadly some EJB+Corba server vendors to have a DD option to shrink
the memory / pooling limitations of the EJB spec'ed behavior of SB's
down to the same as a Corba service, but this is not universal.
Any experiences and vendor feed back?
Thanks,
curt
Curt Smith
Z-Tel
email: [EMAIL PROTECTED]
work: 404-237-1166 x182
FAX: 404-237-1167
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
