Section 9.4.2 of the spec says: "The Container must ensure that the
values of the container-managed fields are set to the Java language
defaults (e.g. 0 for integer, null for pointers) prior to invoking an
ejbCreate(...) method on an instance."
It seems from this that the bean developer *shouldn't* have to handle
this in ejbCreate(), or am I mis-interpreting something?
Thanks,
Dale
================================
Dale V. Georg
Technical Manager
Indus Consultancy Services
[EMAIL PROTECTED]
(201) 261-3100 x229
================================
Rickard �berg wrote:
>
> As you note, the EJB spec makes an explicit note that instances may be
> reused.
>
> It does not make any explicit notes that initial values are to be reset.
>
> Hence, implicitly you as a bean developer knows that you will have to
> handle this in ejbCreate in order to make portable beans. Some
> EJB-servers may be forgiving and will reset these values, or will create
> a new instance each time, but some may not.
>
> There is no bug in the spec, and there is no bug in the EJB-server you
> are using. The only bug here is that you are not taking care of the bean
> contract properly by not setting all CMP fields upon create.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
> ===========================================================================
> 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".
