Change Notes item #850891, was opened at 2003-11-28 22:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=850891&group_id=22866
Category: JBossCMP Group: v3.2 Status: Open Priority: 5 Submitted By: Alexey Loubyansky (loubyansky) Assigned to: Nobody/Anonymous (nobody) Summary: <check-dirty-after-get> Initial Comment: A <cmp-field> in jbosscmp-jdbc.xml has got an optional <check-dirty-after-get> element which can contain true or false. <cmp-field> <field-name>myCMPField</field-name> <check-dirty-after-get>true</check-dirty-after-get> </cmp-field> If field's type is mutable and its value can be changed without invoking its setter, e.g. myBean.getMyCMPField().setValue(), the field should have check-dirty-after-get set to true. Value true means that the field will be checked for dirty state at synchronization time even if only the getter was invoked in a transaction. By default, check-dirty-after-get is set to false only for primitive, its wrapper and java.lang.String types. WARN: if the BLOB type is immutable the check-dirty-after-get should be false. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=381174&aid=850891&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
