Hi,
Leonardo Uribe píše v Pá 03. 06. 2011 v 15:38 -0500:
Hi
2011/6/3 Martin Koci martin.kocicak.k...@gmail.com:
Hi,
the idea seems very good - but when is decided that expression does not
uses some variable resolved by VariableResolver?
Inside VariableMapperWrapper.resolveVariable.
Hi,
what problem is it? I know about excessive rendered evaluation:
JAVASERVERFACES_SPEC_PUBLIC-941. value at EditableValueHolder can be
evaluated 2x during one request/response.
If it is another problem, can you create a jira issue, please?
Thanks,
Kočičák
Kito Mann píše v Pá 03. 06. 2011
On Sun, Jun 5, 2011 at 9:35 AM, Martin Koci
martin.kocicak.k...@gmail.comwrote:
Hi,
what problem is it? I know about excessive rendered evaluation:
JAVASERVERFACES_SPEC_PUBLIC-941. value at EditableValueHolder can be
evaluated 2x during one request/response.
If it is another problem, can
Ah, okay. Thanks for the explanation, Leonardo.
---
Kito D. Mann | twitter: kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info | twitter:
jsfcentral
+1 203-404-4848 x3
* Listen
Hi
Checking this patch I founded one use case where the hack proposed could fail:
c:if test=#{somecondition}
c:set var=myvar value=somevalue/
/c:if
!-- code that use myvar --
I found it in this link:
http://seamframework.org/Documentation/CreatingACompositeAjaxifiedForm
In this case,
