|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
One thing we need to be very careful about it is features that need the same bytecode manipulation. Here, for example, we have dirtiness tracking needing persistent field interception. However, "partial loading" support will need persistent field interception also. We just need to make sure that those things are coordinated.
I am curious if you tried this yet. If so, did it work? I am missing where you hook in the dirty checking so that it is called for each persistent-attribute change.