[ 
https://issues.apache.org/jira/browse/EMPIREDB-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015020#comment-17015020
 ] 

Rainer Döbele commented on EMPIREDB-320:
----------------------------------------

In order to come clean with recent changes to the InputTag and ControlTag an 
API-Change is required for API-change for InputControl.updateInputState 
replacing parameter save (boolean) by phaseId.
i.e. was

{{void updateInputState(List<UIComponent> compList, InputInfo ii, FacesContext 
context, boolean setValue)
}}

but should rather be:

{{{color:#172b4d}void updateInputState(List<UIComponent> compList, InputInfo 
ii, FacesContext context, PhaseId phaseId){color}}}

{color:#172b4d}Inside the current condition:{color}

{{{color:#172b4d}if (setValue){color}}}

should be replaced by:

{{if (phaseId==PhaseId.RENDER_RESPONSE)}}

The method is called in three different JSF lifecycle phases:
 # APPLY_REQUEST_VALUES
 # PROCESS_VALIDATIONS
 # RENDER_RESPONSE

Some actions do only have to be performed in certain phases.

 

> JSF Input skip default JSF input validations
> --------------------------------------------
>
>                 Key: EMPIREDB-320
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-320
>             Project: Empire-DB
>          Issue Type: Bug
>          Components: JSF2 Extensions
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>            Priority: Minor
>
> When validating values of e:input or e:control tags, skip the default 
> validations of the child input components.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to