No, I'm much more pragmatic ;). I'm saying that if there are
2 transactions that are happening in parallel, with a single
database in the background, you need to a) mark any method
that updates a database as a transactional, and b) if those
methods can result in updating the same rows, it's safer
to use version consistency to avoid overriding values from
one transaction with those from another transaction.
HTH,
-marina
Peter A. Murray wrote On 09/20/06 14:48,:
> So you are saying the "transaction" will deal with horizontal scaling of
> the Appserver?
>
> Black box magic which come with using JEE.
>
> Peter
>
> On Wed, 2006-09-20 at 14:18 -0700, Marina Vatkina wrote:
>
>>Peter,
>>
>>You must use transaction settings to make sure that any updates
>>are committed to the database. You'll most probably need to use
>>version consistency to make sure that any conflicts are detected
>>at commit of each transaction. If there are no possibility of
>>parallel updates to the same row, you don't need to do anything
>>special about it.
>>
>>regards,
>>-marina
>>
>>Peter A. Murray wrote On 09/20/06 13:57,:
>>
>>>If I have multiple instances of AS9 running on multiple boxes to scale
>>>horizontally, how dose it impose transaction integrity between the
>>>boxes.
>>>
>>>i.e. I have Entity bean representing a row in a table on the db
>>>I then have user start an update on that Entity on server A and another
>>>user start an update on the same Entity on server B.
>>>
>>>How do I resolve this or will setting up a transaction around the update
>>>of the Entity take care of this?
>>>
>>>Thanks
>>>
>>>Peter
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>