For a bean where there is a lot of deployment information, it seems like a lot
of extra work to have to reenter that deployment information each time you move
the bean to a different server. That is why we need a standard deployment
descriptor (which can be extended, i.e. the way XML is extensible.)
Sincerely,
Anthony Eden
Frank Kohmann wrote:
> Hi!
>
> >You are absolutely correct. This is a design bug of deployment
> >descriptors. It will go away when descriptors are XML-based instead
> of
> >serialized objects. For now there is no way to make a
> server-independent
> >deployment descriptor.
>
> I think it does not make sense to provide a server-independant deployment
> descriptor in regard to identities (or better principals). This always
> depends on the server environment. It does not make sense for a bean
> developer to provide information about special identies allowed to use the
> bean or the bean's methods. He does not kow what identities exist in the
> environment the bean will run in. This kind information always will have to
> be provided by the deployer, since he is the one who knows the special
> server environment. How could this change with the use of an XML
> representaion for the descriptor?
>
> cheers
> Frank
===========================================================================
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".
