[
https://issues.apache.org/jira/browse/MYFACESTEST-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rudy De Busscher updated MYFACESTEST-51:
Resolution: Fixed
Fix Version/s: 1.0.4-SNAPSHOT
Assignee: Rudy
Hi all,
I'd like to discuss something I've been thinking about lately. How to clear
forms easily when validation fails?
Consider this simple case;
h:form
h:messages /
h:inputText value=#{pprBean.firstname} required=true/
h:inputText
[
https://issues.apache.org/jira/browse/MYFACESTEST-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rudy De Busscher updated MYFACESTEST-52:
Resolution: Fixed
Fix Version/s: 1.0.4-SNAPSHOT
Assignee: Rudy
[
https://issues.apache.org/jira/browse/EXTVAL-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rudy De Busscher updated EXTVAL-133:
Resolution: Fixed
Fix Version/s: 1.2.5
2.0.5
Status:
Sounds like a good idea.
But shouldn't that be handled via the JSF EG?
Such a behaviour would need to be written in the spec to be reliable, isn't?
LieGrue,
strub
--- On Mon, 5/30/11, Cagatay Civici cagatay.civ...@gmail.com wrote:
From: Cagatay Civici cagatay.civ...@gmail.com
Subject: Clear
Hi,
javax.faces.component.EditableValueHolder.resetValue() and/or listener
like
http://myfaces.apache.org/trinidad/trinidad-api/tagdoc/tr_resetActionListener.html
does not solve it?
Kočičák
Mark Struberg píše v Po 30. 05. 2011 v 13:19 +0100:
Sounds like a good idea.
But shouldn't that be
[
https://issues.apache.org/jira/browse/MYFACES-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041123#comment-13041123
]
Martin Kočí commented on MYFACES-3157:
--
classes with isRendered() in myfaces -impl
Hi,
problem described in MYFACES-3157 applies for all cases where renderer
reads property from child component. I think that only correct way in
push child to EL before:
child.pushComponentToEL()
Object value = child.getValue();
String style = child.getStyle();
child.popComponentFromEL()
Is
[PERF] TagAttributeImpl part II: object allocations (cache ELExpressions)
-
Key: MYFACES-3160
URL: https://issues.apache.org/jira/browse/MYFACES-3160
Project: MyFaces Core
[
https://issues.apache.org/jira/browse/MYFACES-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonardo Uribe updated MYFACES-3160:
Status: Patch Available (was: Open)
[PERF] TagAttributeImpl part II: object
Hi
There is a patch proposed (after many months thinking about it),
according to the discussion on:
http://markmail.org/message/kca64ojdvb6em367?q=%5Bcore%5D+performance:+TagAttributeImpl+part+II:+object+allocations
here:
https://issues.apache.org/jira/browse/MYFACES-3160
The idea is cache
Hi
I think it is correct to do that. After all, it will not cause any
side effects., but I it could be better if you wrap those calls in a
try {} finally block.
regards,
Leonardo Uribe
2011/5/30 Martin Koci martin.kocicak.k...@gmail.com:
Hi,
problem described in MYFACES-3157 applies for all
12 matches
Mail list logo