myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Aranda (JIRA)" <>
Subject [jira] Resolved: (MYFACES-1765) h:selectOneMenu doesn't call setter
Date Sun, 02 Dec 2007 18:45:43 GMT


Bruno Aranda resolved MYFACES-1765.

    Resolution: Cannot Reproduce
      Assignee: Bruno Aranda

Cannot reproduce this issue. What do you refer when saying tomahawk 2.0? The latest tomahawk
released, 1.1.6, works fine with myfaces 1.2.1-SNAPSHOT (and the tomahawk snapshot too).
Maybe do you refer to the tomahawk I branched to play a bit with the autogeneration of components?
If so, that was ongoing work and as far as I know it never worked.

Thanks for reporting Wolf,



> h:selectOneMenu doesn't call setter
> -----------------------------------
>                 Key: MYFACES-1765
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions:  1.2.0
>         Environment: MyFaces 1.2.1 - Tomahawk 2.0 Snapshot - Facelets 1.1.13
>            Reporter: Wolf Benz
>            Assignee: Bruno Aranda
>            Priority: Blocker
>             Fix For: 1.2.1-SNAPSHOT
> I don't know whether this error only occurs in combination with facelets, but this is
what happens: the "return value: of a h:selectOneMenu in always "null" in the sense that the
SETTER IS NEVER CALLED (-> value stays null)
> So for:
> <h:selectOneMenu value="#{testOverviewBean.compoundCodeFromMenu}" valueChangeListener="#{testOverviewBean.fillTestSeqNrs}"
> 		<f:selectItem itemLabel="Choose One" itemValue="choose_one"/>
> 		<f:selectItems value="#{utilBean.compoundCodes}" />
> </h:selectOneMenu>
> ... the setCompoundCodeFromMenu() is never called, which always leads to NPEs later on.
> As this is one of the few core components ("h:"), I think labelling it "blocking" is
> -Wolf 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message