The class would probably be delivered with the deployment tool in the first
place. There is one deployment tool for each vendors container. Thus, each
time you deploy to a different vendor's container, you will have to respecify
all of the deployment information (yuck!) This needs to be standardized in a
better way.
This is probably one of the reasons that the next spec will use XML...
Extended thoughts on this from anyone?
Sincerely,
Anthony Eden
Y Hatsuyama wrote:
> Hi.
> I meets another problem.
> JDK mentions java.security.identity is abstract class.
> That means deployment tool for EJB requires the identity class
> that implements java.security.identity class to desirialize access control
> entry.
> I think this identity class depends on the jar file creator.
> Does the EJB jar file include the identity class?
> If it does not, how does the deployment tool know the class?
>
> Please tell me about this.
>
> Thnaks
>
> Mar 18th 1999
> Y Hatsuyama
>
> ===========================================================================
> 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".
--
Webmanager
Groupe ESSEC
Avenue Bernard Hirsch, BP 105
95021 Cergy Pontoise Cedex France
[EMAIL PROTECTED]
===========================================================================
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".
