-
1. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
grandtourer May 21, 2010 2:24 AM (in response to ryoung2504.ryoung.dsl.pipex.com)Yes I have encountered this as well. I would add that I am using JBoss AS 6 M3 with JSF2 and Richfaces. I didn't investigate further whether this was a JSF2 issue or Seam. I'll poke around and see if s:selectItems has changed between versions.
Perhaps you should log a JIRA on this.
-
2. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
cbensemann Jan 10, 2011 11:07 PM (in response to ryoung2504.ryoung.dsl.pipex.com)Just encountered this problem myself with Seam 2.2.1.CR3 and JBoss 6 CR1. There is a jira open for it here: https://issues.jboss.org/browse/JBSEAM-4654 that links back to this page. This code used to work uner AS 5.1 but not under 6. Does anyone know a work around for this? If not I may have to roll back to AS 5.1.
thanks
Craig -
3. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
cbensemann Jan 10, 2011 11:36 PM (in response to ryoung2504.ryoung.dsl.pipex.com)Ok. So forcing AS 6 to use Mojarra 1.2 instead of 2.0 fixes the problem so it must have to do with the way converters are used in jsf 2.0???
-
4. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
cavani Jan 11, 2011 9:59 AM (in response to ryoung2504.ryoung.dsl.pipex.com)I describe my fix on JIRA comment but I am not sure that it is the correct solution.
Thanks,
-
5. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
fivalo Feb 2, 2012 5:03 PM (in response to ryoung2504.ryoung.dsl.pipex.com)Hi
You can forde to use Mojarra 1.2 but the Jboss Administration Console wouldn' t work with this change.
Have you find other workaround?
Thanks
Fido
-
6. Re: noSelectionLabel failing to produce noSelectionValue markup on 2.2.1.CR1
fivalo Mar 16, 2012 6:47 PM (in response to fivalo)Hi
When the server starts it uses the JSF 2.0 version, but any app can use its own version, only configure the web.xml
<context-param>
<param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name>
<param-value>Mojarra-1.2</param-value>
</context-param>
This says the app use the Mojarra 1.2 versión allowing jmx-console and web-console works correctly.
This works in Jboss6.1 in all JSF versions that have this directories:
jboss_home\server\domaiin\deployers\jsf.deployer\*
Bye