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?
- 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 Mike Kienenberger
- Re: Value is not a valid option Khurram Ahmed
- Re: Value is not a valid option Mike Kienenberger
- Re: Value is not a valid optio... Khurram Ahmed
- Re: Value is not a valid o... Travis Reeder