Hi,
Yes. creating an instance of Identity is vendor specific because, Identity is
defined
as an abstract class in JDK.
EJB 1.1. has modified this call instead to take a java.lang.String as an
argument so that
you get away from vendor specific calls to create an identity. Moreover,
java.security.Identity has been deprecated in Java 2.
Thanx,
Harish
Java 2 Enterprise Edition
JavaSoftware Division.
Mark Mendel wrote:
> Per 1.0 spec, EJBContext.isCallerInRole() takes an Identity as a parameter.
> Identity is an abstract class. JDK1.17B.
>
> Is this something that is vendor specific? OK, then, <vender>how do I it
> with WebLogic?</vender>
>
> ===========================================================================
> 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".
