Laird Nelson wrote:
>
> This tells me that for the short- to medium-term I should just accept
> the fact that authentication is broken and that the EJB server might not
> know what principal is calling it, and so I should basically code my
> first-generation beans extraordinarily defensively so that they don't
> rely on the so-called security features of EJB, which aren't there yet.
I dont think that is the case. The EJB Server vendor could still provide a way to do
that but your code would not be portable.
>
> ===========================================================================
> 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".
