I think the isModified would be the better way to go. This forces the bean
developer to do something explicite. Using get*() checks might give
someone a nasty surprise if the code a getter with side effects, and if
that person is a deployer who didn't write the beans, it could take quite
a while to figure out that all they need to do is turn off that
optimization.
On Sun, 8 Oct 2000, Rickard [iso-8859-1] �berg wrote:
> Hi!
>
> Aaron Mulder wrote:
> > Well, you could always specify no transaction for your
> > "getters" to avoid this...
>
> No, that wouldn't help since we always call ejbStore after methods
> without tx's have been executed (as per the spec). The database
> interceptor will either have to be updated to avoid store on get*()
> calls (as it used to), or perhaps add support for isModified() checks.
>
> /Rickard
>
>
--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
