If only our Corba services mapped to ??? what ?? EJB
session beans, so simply.
EJB does not allow all of the things that (maybe most??) folk's
corba services do:
- Open files, create back ground threads,
- Create references to Singleton helper objects
- Create our own DB connection pools (a Singlton)
So the strategy of just re-editing Service.idl to be a
remote interface, recompile, deploy and wham, you're now
an EJB just isn't that simple.
In fact I've more or less resigned to this being impossible
and searching (benchmarking) EJB server vendors who support
both Corba services and EJB's in the same server. We'll not
even bother with converting most of our corba services to
EJB. Why??? What's the pay back?? It's not there period.
Some EJB+Corba products support clustering and HA features
for both Corba services and EJB's so there's no value if
your corba services aren't transactional in the first place.
Just my observations so far.
curt
Curt Smith
Z-Tel
email: [EMAIL PROTECTED]
work: 404-237-1166 x182
FAX: 404-237-1167
> hi, to create EJBs you can just use the sun's reference
> implementation of
> the ejb server (i think it comes with j2ee-sdk). Both CORBA
> and EJBs work
> the same way. Both of them talk via stubs to their respective
> skeletons
> connected to the remote object. However, CORBA uses IIOP to
> talk between
> stubs and skeletons and EJBs use RMI. So model the CORBA
> services that you
> already inside of an EJB and then instead of using IDL to
> create interfaces,
> you just have to compile the code using the j2ee-sdk. this
> create the stubs
> and skeletons for you. (in CORBA the IDL Compiler would
> create the stubs and
> skeletons). Hope this to see how both of them map.
>
===========================================================================
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".
