> Chris Raber wrote:
>
> > an EJB server gives them life in the context of RMI or CORBA/IIOP.
>
> Not all EJB servers support CORBA, and I'd check for that feature
> when shopping for an EJB server.
>
Exactly my point!
> > The only CORBA specific code would be if you have non-EJB clients which
> are
> > CORBA based, talking to EJBs.
>
> What does the "CORBA specific code" do in this case?
>
I was refering to CORBA clients that are calling your EJBs.
> > > - is (will) there a (automatic) way to use CORBA instead of RMI later
> > > (just redeploying on a CORBA-capable EJB-server/container) ?
> > >
> > Yes. This is true today!
>
> True today, but just how easy is it to re-deploy from RMI to CORBA?
>
Trivial. Non-issue. EJB is protocol nuetral. One programs to Java interfaces
and
the EJB server builds the underlying protocol layers.
> Does the bean's jar need to be rebuilt?
>
No, the protocol stuff happens when the jar is deployed to the server. The
vendor
neutral jar format is just that, vendor neutral.
> ==========================================================================
> =
> 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".
===========================================================================
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".