I don't have an answer for you, but I came across a similar problem a few
days ago with Firefox.  I assume it's Firefox since you mentioned opening a
new tab.

When I access our site I get auto-logged-in with a cookie and get a new
session as expected.  If I open a new tab and repeat the same URL, I get
another view onto the *same* session.  No new login.  I can easily reproduce
the nasty behavior you're seeing, without being as tricky as right-clicking
a link to open it in a new tab.

In fact if I start another instance of Firefox (a new browser window, not a
tab) the same thing happens.  Doing this in IE starts a new session.  I've
done a little googling and found another user complaining about this but no
quick fixes.  Hoping someone else in this list has some expeirence with
this.


----- Original Message ----- 
From: "Patrick Casey" <[EMAIL PROTECTED]>
To: "'Tapestry users'" <[email protected]>
Sent: Saturday, May 07, 2005 2:47 PM
Subject: Multiple Instances of the Same Page and Persistence


>
> I'm having a bit of a problem with a manually persisted property.
>
> I have a list of users.
> If somebody selects one user, I bring up an edit form and persist a
> key value.
> If the user presses save, the edit form object uses the persisted
> key to reload the object before pushing the user's edits in.
>
> It works fine, but only if there's only *one* edit page up. Example:
>
> I have a list of users.
> User pressed "open in new tab" on John Smith -> persist key #43
> User pressed "open in new tab" on Jane Doe -> persist key #86 //
> doh!
> User now changes John Smith's data on the form and presses save.
>
> The currently persisted key for the edit form though is 86, not 43,
> so we end up overwriting Jane Doe's information instead of updating John
> Smith's information.
>
> I've resolved this problem by not using the Tapestry persistence
> layer and instead stuffing the key into a hidden field on the form, but it
> strikes me there has to be a way to make it work and still use the
> persistence layer.
>
> Can anyone offer some advice here? Is this just a case where I can't
> use Tapestry persistence?
>
> --- Pat
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to