Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (athena.apache.org: domain of mwessendorf@gmail.com
 designates 209.85.219.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=kcAZdr23/kAUfKipVxeI36uqDPNFgoXXh/gj1OPQdXZhOWByd1oaVb9Miq/+7yOwuH
         mgnFzO+UcIlzMJTvmP51Cu03j1x4qYwuBn80x7Zcjq4IeRPnBMnKpphlnhpdW3tRWmHz
         q0GDLIvSJ0du2qDzjr4/1vzKJzb0LdkOu9GvE=
MIME-Version: 1.0
Sender: mwessendorf@gmail.com
In-Reply-To: <CCBF12448B0015418E9834860AA79F7E0F2CB392@pepex1.pepstores.com>
References: <CCBF12448B0015418E9834860AA79F7E0F2CB392@pepex1.pepstores.com>
Date: Tue, 25 Aug 2009 13:36:11 +0200
Message-ID: <71235db40908250436w36b092ffmcb2d98156630725e@mail.gmail.com>
Subject: Re: [Trinidad] Ensure Correctness of Data.
From: Matthias Wessendorf <matzew@apache.org>
To: MyFaces Discussion <users@myfaces.apache.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 24, 2009 at 6:07 PM, Leon Dorfling<LEOND@pepkorit.com> wrote:
> We are developing our first Java project using Trinidad.
>
>
>
> We are trying to resolve, a seemingly simple problem we have encountered,
> but due to our lack of experience have not found the optimal solution.
>
>
>
> Our problem is, 2 users are viewing the same data. User1 deletes a record
> from the database. The deleted record has not yet been deleted from user2=
=92s
> page. Subsequentley user2 tries to update the record deleted by user1. Us=
er2
> clicks on the record (deleted by user1) and navigates to a page to update
> the record. The update page is rendered with data for the row after the
> deleted row in the table.
>
>
>
> How do I ensure that if user2 tries to update a deleted record, he is eit=
her
> warned that the records no longer exists or the data is refreshed before =
he
> invokes an update process.

you need to implement a smarter solution here by your self. EG using
unique IDs, so that one could not load a deleted object by a (wrong)
ID.

Another would be to implement something like optimistic locking, see here:
http://api.rubyonrails.org/classes/ActiveRecord/Locking/Optimistic.html
(no, there is no need to use ActiveRecord for that. Can be done with
anything you are
using in the back-end).

But basically your application (design) has to take care of this.

-Matthias


>
>
>
> Thanks.
>
>
>
> Leon Dorfling
> Pepkor IT
> email : leond@pepkoritcom
> tel : (021) 937 9225
> fax : (021) 937 9213
> cell : 083 6789 270
>
>
>
> Pep a division of Pepkor Retail Limited.The legal status of this
> communication is governed by the terms and conditions
> published at http://www.pepstores.com/cms/view/content/email_disclaimer,
> which terms and conditions relate,inter alia, to confidentiality and
> limitation of liability and include the names of directors and the
> registration number of the company.


--=20
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf