Ok i didnt open a jira issue yet but i found out a work around the hard
way, i read the discussion on the mailing list just prior to fixing
this particular bug and it turned out that it had something to do with
the behavior of converters which was buggy, so i removed all converters
from the project and the bug has disappeared however this cant be a
viable or an elegant solution in the long run, and this bug has already
been fixed in the source code 3 to 4 days ago and released at least
that is the impression i got from jira. The bug i am referring to is
Bug 669 in my faces and the discussion i am referring to can be found
here
http://issues.apache.org/jira/browse/MYFACES-669
- Re: Value is not a valid option Khurram Ahmed
- Re: Value is not a valid option Mike Kienenberger
- Re: Value is not a valid option Khurram Ahmed
- Re: Value is not a valid option Travis Reeder