We're using Jboss 3.0.4 with CMP 2.0. All our Entity beans have a CMP-field "modified" to be able to track updates on entities by a timestamp.
Now I thought the ejbStore-Method would be the best place for calls like setModified(timestamp) - but that does not work properly because ejbStore is called even though only a read access takes place. The result is that the timestamp is updated continuously and therefore is useless.
I found some hints about
- an isModified method
- transaction attributes
Well, I don't know how to use isModified with CMP. I think it's intented for BMP only and I don't want that kind of appserver specific code in our sources.
"tuned-updates" seems to be for use with older Jboss versions only. We have no jaws.xml file and according to the dtd of the jbosscmp-jdbc.xml we can't use that tag there.
I tried all combinations of transaction attributes of our business methods in the session beans and the corresponding entity beans that are involved in read actions. This all resulted in no change of the behaviour.
I think it's a bit weird, or am I totally wrong with my approach of maintaining a timestamp in every db table this way?