Hello,
the problem is, how in EJB 1.1 do you identify methods
that modify the CMP fields ? This is OK in CMP 2.0, where
the CMP fields can only be accessed by "accessor methods",
setXXX and getXXX. But in EJB 1.1, you cannot assume
that the bean developer will provide setXXX methods, and that
she/he will modify the CMP fields only by the way of these setXXX
methods.
Best Regards,
François
[EMAIL PROTECTED] wrote:
> There is the possibility to do performance optimization in JOnAS by implementing the
>set/reset of isDirty. Quite poor, with
> CMP the user has to set/reset the flag manually, so on every bean on every set
>method I have to write code to dirty that
> flag.
>
> My idea is, why not changing GenIC (maybe with a parameter, e. g. -optimizeCmp) to
>create code automatically in the form
> "this.dirty=true" in every set method and "this.dirty=false" in ejbLoad (and at the
>end of ejbStore)?
>
> This would easen the job of optimizing and would be a good default implementation.
--
==================================================================
Francois EXERTIER Evidian (Groupe Bull)
1, rue de Provence, BP 208, 38432 Echirolles cedex, FRANCE
mailto:[EMAIL PROTECTED]
http://www.evidian.com/jonas http://www.objectweb.org/jonas
Tel: +33 (0)4 76 29 71 51 - Fax: +33 (0)4 76 29 77 30
==================================================================
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
