-
1. Re: immediate=
sergeysmirnov Oct 18, 2007 3:48 PM (in response to hgf)
The workaround is very simple:
do not use ajaxSingle="true" if immediate="true"
because it just does not make any sense in this combination. ajaxSingle="true" the same as immediate="true".
No plan to change the behaviour.
There is a plan to resolve the fighting between ajaxSingle="true" and immediate="true" when they try to do the same things different ways.
The version is 3.2.0 -
2. Re: immediate=
hgf Oct 18, 2007 4:06 PM (in response to hgf)Hi Sergey,
thank you for answering.
I fear that I've did not understand the concept. I thought that ajaxSingle="true" defines the local component as region and immediate="true" switches of the validation in JSF. Both features are very different to me.
Perhaps you find the time to explain why this combination does not make send.
Reagards
HGF -
3. Re: immediate=
alexsmirnov Oct 18, 2007 5:07 PM (in response to hgf)This issue will be fixed in the next releases ( both 3.1.x and 3.2.0 ).
-
4. Re: immediate=
alexsmirnov Oct 18, 2007 5:29 PM (in response to hgf)See http://jira.jboss.org/jira/browse/RF-1149 for a status.
-
5. Re: immediate=
hgf Oct 18, 2007 6:22 PM (in response to hgf)I'm very thankful for this hint. Even if it is nearly empty yet. Do you have another hint about the problem in using immediate="true" combined with ajaxSingle="true"? As I wrote before both features are very different to me. Because of that I don't understand why not to use both.