Some elements of the EJB DD are dependent on its implementation.
Development and deployment tools will help keep these in sync. It was an
explicit EJB design decision to limit EJB code to the minimum needed.
It would have been a bad design decision to use encoding in Java as a
way to make deployment info 'read-only'. It is much clearer to keep code
and deployment info clearly partitioned.
-- Mark
Laird Nelson wrote:
>
> Assaf Arkin wrote:
> > Confusing name. The deployment descriptor is created by the bean
> > developer, the bean developer gets to specify which type of bean it is.
> > The deployment descriptor is *not* created or modified at deployment
> > time.
>
> *Blink* *blink* so why aren't its attributes specified in the bean code,
> or as the results of public final methods?
>
> What a weird specification.
>
> Cheers,
> Laird
>
> ===========================================================================
> 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".
