> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of marc
> fleury
> Sent: Thursday, June 14, 2001 11:34 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] No storeEntity before ejbFind<METHOD>
>
>
>
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill
> |Burke
> |Sent: Thursday, June 14, 2001 9:55 AM
> |To: [EMAIL PROTECTED]
> |Subject: RE: [JBoss-dev] No storeEntity before ejbFind<METHOD>
> |
> |
> |So....I'll check this stuff in??
>
> Yes, with the understanding that if the user doesn't define
> "isModified" or
> "tunedUpdates=true" then they are paying a heavy price for this feature.
> (double serialization).
>
>
Yeah, double serialization, but isn't keeping an isUpdated table just
overkill and a pain in the ass?  Maybe not I guess, set the flag to true for
each entity after you do the finder synch. Set it to false after every
method invocation that could possibly change the state of the entity.
You're right, I'll put this in....Thanks for discussing this issue.

On another note, I view this change not as a "feature", but rather a bug
fix, an ejb spec violation.  It's kind of significant when I think about it.
If you modify an entity within a transaction, a subsequent finder query
should be able to pick up the entity change.  The example from before,
should work, but doesn't with the current version of jboss.  Also common
sense dictates it should work as well, (at least in my messed up brain).

----------------------------
begin transaction

Bean b = findByPrimaryKey(...)
System.out.println("flag = " + b.getFlag()); // prints flag = 1
b.setFlag("0")

Enumeration = findByAllBeansWithFlagEqualToOne(....) // where flag = '1'

// We assume Bean b is not in the Enumeration, but it is.

end transaction
----------------------------

BTW, thanks for reviewing all this stuff.

Bill



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to