Definitely yes, if you provide simple testcase reproducing the issue I will look at it immediately and try to fix or apply mentioned patch.
Test Case using ../examples-ee6/ui: Remove ui:debug tag in template.xml and deploy
1) For Enum in "Title field::
a) Generated html: <option selected="selected">Please select</option>
b) Error: Caused by javax.servlet.ServletException with message: "No enum constant org.jboss.seam.example.ui.Person.Honorific.Please select"
2) For Entity in "Continent of Birth"
a) Generated html: <option selected="selected">Please Select...</option>
b) Error: For input string: "Please Select...": java.lang.NumberFormatException: For input string: "Please Select... at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [rt.jar:1.7.0_03]
I tried to remove line
<ui:debug id="debug" />
from examples/ui/ui-web/src/main/webapp/template.xhtml but no errors like you described are shown in deployed application on JBoss AS 7.1.1.Final on my local environment.
Haven't you changed by chance anything additional?
Strange. No, that's all I did. Deployed without <ui:debug id="debug" /> it is working for me, with <ui:debug id="debug" /> removed I have the behaviour described. I notice that you say you changed examples/... while I did my testing with examples-ee6/.. on jboss AS 7.1.1.Final as well. Edit: I realized it has now been renamed.
I will check this with a fresh install as well.
I have now re-tested this with fresh installations of:
Still the same behaviour as described.
With ui-debug generated code is: <option value="org.jboss.seam.ui.NoSelectionConverter.noSelectionValue" selected="selected">Please Select...</option>
Without ui-debug generated code is: <option selected="selected">Please Select...</option>
Pressing submit without doing selections will generate above mentioned errors.
Many thanks for fixing this so quickly. I appreciate it a lot.
Try to add this parameter to your web.xml
Juan, thanks for your input. I already had this parameter set though, when I reported the error so that was not a solution. The problem is solved though in the ticket Marek is referring to, as verified when using 2.3.1-SNAPSHOT.