> Just 2 question though, 1> are all EJB clients( non-HTTP based ) written in
> Java? The WebLogic's assertion seems to indicate that.
Absolutely not, and Eduardos reply does not state that. If a particular
vendor wants to support non-Java clients (i.e. CORBA-clients), then that
vendor should add support for that through RMI/IIOP. But this feature
should not be mandatory. It doesn't make any sense to have it be
mandatory. EJB != CORBA. If you want to interoperate with CORBA, fine,
go ahead, but don't assume everybody wants to do that.
> 2> Dont you have
> cases where EJB objects have to talk to legacy ( read non-java )
> applications.
Aboslutely, in which case you would want to use a EJB-server that
supports this feature. In the future, however, this type of
functionality will be provider through the Connector API, so you will be
able to plug it into any EJB-server. Hence, the EJB-server does not have
to have "native" support for it; it can be added through a standard
interface.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
