> IMHO a better way to introduce interoperability is to have API's that
> lets a stub figure out which security id and tx id is associated with
> the current thread. This way that information can be extracted and
> forwarded in any way it pleases. The only requirement is that the client
> has installed the packages needed to support the stubs of the server.
> This will of course make it troublesome to be able to call a server from
> a C++ client, but in those cases I would simply use a server that indeed
> uses IIOP as protocol. We would still have interoperability between EJB
> servers.
Sorry, but I really don't see the problem. In our tests RMI stubs that
propagation tx and security work very well with IIOP (where propagation
is delegated to the ORB) and same-VM (where propagation is left to the
SPI).
arkin
>
> Comments? If RMI-IIOP is mandated *and* my fear that it is only possible
> to have one protocol at a time, EJB-servers will be severely restricted
> in the ways it may provide cool functionality, such as transparent
> fault-tolerance and load-balancing.
>
> /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".
>
> ===========================================================================
> 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".
