> From: A mailing list for Enterprise JavaBeans development
> Maybe my mind works differently, but to me, the two statements:
>
> "BEA does not encourage users to write non-portable code."
>
> and:
>
> "In our RMI/T3 implementation, PRO.narrow is a no-op."
>
> are contradictory. To me, making PRO.narrow a no-op encourages
> users to write non-portable code.
I fail to see the implication. Users should just stick to the standard and use
PRO.narrow(). Whether it's a no-op or not is implementation detail and has no
effect whatsoever on the user's code.
--
Cedric
===========================================================================
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".
