You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Khurram Ahmed <kh...@gmail.com> on 2005/12/06 06:20:03 UTC
Value is not a valid option
We have developed an application using myfaces 1.0.9, however due to some
critical bugs in 1.0.9 we were forced to upgrade to myfaces 1.1.0 with the
same code base that was working with the previous version of myfaces 1.0.9.
This was when we ran into the "Value is not a valid option" bug on a page
containing several drop down boxes and the JSF calendar component. After
carrying out some research it was discovered that the bug had been fixed in
the nightly build of 2nd December 2005 so we downloaded the latest nightly
build of myfaces 1.1.1 (that of 4th December 2005), however we are running
into the same "Value is not an option" error again. Can someone verify if
the bug has really been fixed? Are there any workarounds?
Re: Value is not a valid option
Posted by Travis Reeder <tr...@gmail.com>.
We were just discussing this issue on the dev list about not providing
good logging information when these types of errors occur. I'm hoping
we can get this resolved soon so you can put your converters back in.
Travis
On 12/7/05, Khurram Ahmed <kh...@gmail.com> wrote:
> No the problem wasnt fixed i had to alter my code base to not use
> converters in myfaces which are the root of the problem.
>
Re: Value is not a valid option
Posted by Khurram Ahmed <kh...@gmail.com>.
No the problem wasnt fixed i had to alter my code base to not use
converters in myfaces which are the root of the problem.
Re: Value is not a valid option
Posted by Mike Kienenberger <mk...@gmail.com>.
So when you use the latest nightly, is the problem fixed for you?
On 12/7/05, Khurram Ahmed <kh...@gmail.com> wrote:
> 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
Posted by Khurram Ahmed <kh...@gmail.com>.
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
Posted by Mike Kienenberger <mk...@gmail.com>.
Can you create a simple example and open a JIRA issue?
One thing you can do to investigate the error is set a breakpoint
wherever the "Value is not a valid option" message is generated. This
appears to be in
api - javax.faces.component.UISelectOne.validateValue()
Line 54 in yesterday's svn.
On 12/7/05, Khurram Ahmed <kh...@gmail.com> wrote:
> I downloaded the latest myfaces nightly build that of 6th December 2005 and
> the problem still persists. Any solutions or workarounds? Lack of any stack
> traces is making it infuriatingly difficult to even track the bug.
Re: Value is not a valid option
Posted by Khurram Ahmed <kh...@gmail.com>.
I downloaded the latest myfaces nightly build that of 6th December 2005 and
the problem still persists. Any solutions or workarounds? Lack of any stack
traces is making it infuriatingly difficult to even track the bug.
Re: Value is not a valid option
Posted by Mike Kienenberger <mk...@gmail.com>.
Khurram,
I suspect that if the bug was fixed in the Dec 2nd nightly that it did
not make it into the Dec 4th release of 1.1.1. Try grabbing one of
the nightlies and see if it's fixed for you.
On 12/6/05, Khurram Ahmed <kh...@gmail.com> wrote:
> We have developed an application using myfaces 1.0.9, however due to some
> critical bugs in 1.0.9 we were forced to upgrade to myfaces 1.1.0 with the
> same code base that was working with the previous version of myfaces 1.0.9.
> This was when we ran into the "Value is not a valid option" bug on a page
> containing several drop down boxes and the JSF calendar component. After
> carrying out some research it was discovered that the bug had been fixed in
> the nightly build of 2nd December 2005 so we downloaded the latest nightly
> build of myfaces 1.1.1 (that of 4th December 2005), however we are running
> into the same "Value is not an option" error again. Can someone verify if
> the bug has really been fixed? Are there any workarounds?
>
>