Not sure Wolfgang. It's marked as patch available but I don't actually
see a submitted patch. Do you want me to cancel the patch so it's once
again open?
Scott
[EMAIL PROTECTED] wrote:
Hi,
has this been fixed or is there a workaorund available. .we also come
into a similar situation:
While a popuo dialog (lightweight) is coming up, one can tab out in
the main window and stay there and do lots of bad things.. ;(
Best wishes,
Wolfgang
*"Dhaliwal, Balvindar " <[EMAIL PROTECTED]>*
31.07.2008 15:25
Bitte antworten an
"MyFaces Development" <[email protected]>
An
Matthias Weßendorf (JIRA) <[email protected]>
Kopie
Thema
RE: [jira] Updated: (TRINIDAD-1157) Blocking attribute of
coomandButton does not work
Hi Matthias,
Has this issue been fixed in 1.2.8? I am using trinidad version 1.2.8
and blocking does not work with IE6.
Thanks,
Bal.
-----Original Message-----
From: Matthias Weßendorf (JIRA) [mailto:[EMAIL PROTECTED]
Sent: 31 July 2008 13:13
To: Dhaliwal, Balvindar [CMB-IT]
Subject: [jira] Updated: (TRINIDAD-1157) Blocking attribute of
coomandButton does not work
[
https://issues.apache.org/jira/browse/TRINIDAD-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1157:
-----------------------------------------
Fix Version/s: (was: 1.2.8-core)
> Blocking attribute of coomandButton does not work
> -------------------------------------------------
>
> Key: TRINIDAD-1157
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1157
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.8-core
> Environment: Weblogic 10 MP1, seam and windows/solaris
> Reporter: Balvindar Dhaliwal
>
> When using the commandButton and commandLink with blocking set to
true, a stateful session bean (ejb3) method is called to return a
result set. When the button is hit successively many times weblogic
throws a LockTimedOut exception - Stateful Session EJBs cannot be used
concurrently. I would expect the blocking attribute to synchronise
the requests, so subsequent button hits would have to wait till the
the previous request is rendered. Is there a workaround for this?
> Please advise.
> Thanks,
> Balvindar
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
