August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3254) <s:selectItems> broken in NumberGuess example

by Stan Silvert (JIRA)

<s:selectItems> broken in NumberGuess example --------------------------------------------- Key: JBSEAM-3254 URL: https://jira.jboss.org/jira/browse/JBSEAM-3254 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.A1 Reporter: Stan Silvert When you run the Numberguess example, you get to a point where the numberGuess page switches to showing a dropdown of choices: <h:selectOneMenu value="#{numberGuess.currentGuess}" id="selectGuessMenu" required="true" rendered="#{(numberGuess.biggest-numberGuess.smallest) le 20 and (numberGuess.biggest-numberGuess.smallest) gt 4}"> <s:selectItems value="#{numberGuess.possibilities}" var="i" label="#{i}" /> </h:selectOneMenu> <h:selectOneRadio value="#{numberGuess.currentGuess}" id="selectGuessRadio" required="true" rendered="#{(numberGuess.biggest-numberGuess.smallest) le 4}"> <s:selectItems value="#{numberGuess.possibilities}" var="i" label="#{i}" /> </h:selectOneRadio> At that point, you will get an IllegalArgumentException as similar to the last comment of JBSEAM-880: java.lang.IllegalArgumentException: Expected a child component type of UISelectItem/UISelectItems for component type javax.faces.SelectOne(selectGuessMenu). Found java.lang.String. com.sun.faces.renderkit.RenderKitUtils.getSelectItems(RenderKitUtils.java:357) If I add a noSelectionLabel to each <s:selectItems> then the IllegalArgumentException will go away, but the values do not populate the dropdown. It looks like there might be something wrong deep inside <s:selectItems> ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3245) Rebuild JExcelAPI with sane logging

by Pete Muir (JIRA)

Rebuild JExcelAPI with sane logging ----------------------------------- Key: JBSEAM-3245 URL: https://jira.jboss.org/jira/browse/JBSEAM-3245 Project: Seam Issue Type: Task Components: Excel Reporter: Pete Muir Assignee: Daniel Roth Fix For: 2.1.0.BETA1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3253) Upgrade to RichFaces 3.2.2

by Pete Muir (JIRA)

Upgrade to RichFaces 3.2.2 -------------------------- Key: JBSEAM-3253 URL: https://jira.jboss.org/jira/browse/JBSEAM-3253 Project: Seam Issue Type: Task Reporter: Pete Muir Priority: Critical Fix For: 2.1.0.BETA1 And test the relevant examples and seam-gen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3085) Renderer is only partially functional when used asynchronously

by Dan Allen (JIRA)

Renderer is only partially functional when used asynchronously -------------------------------------------------------------- Key: JBSEAM-3085 URL: http://jira.jboss.com/jira/browse/JBSEAM-3085 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Reporter: Dan Allen Fix For: 2.1.0.GA The Renderer, which is used to render Facelet templates, is partially crippled when used asynchronously. First of all, it throws an exception while setting up the MockFacesContext() because it tries to retrieve an Application from the real JSF FactoryFinder. That isn't going to work because JSF is not properly initialized. That leads to the second problem, which is that if the template has any JSF component tags, they aren't rendered because its not a real JSF environment. I think the solution is to use JSFUnit to emulate a JSF environment so that the Renderer can be used asynchronous. Otherwise, we cannot send email messages that use JSF components in the background. The second solution is to document that you cannot render JSF markup in your email if used asynchronously. This affects the /examples/mail demo application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2912) Translating Seam into your own language (sl-SI)

by Andrej Marolt (JIRA)

Translating Seam into your own language (sl-SI) ----------------------------------------------- Key: JBSEAM-2912 URL: http://jira.jboss.com/jira/browse/JBSEAM-2912 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: Andrej Marolt I would like to begin the process of translating Seam into Slovenian. (sl-SI) Language: Slovenian Locale: Slovenia -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3192) Refer to enclosing class when enforcing @Restrict

by Pete Muir (JIRA)

Refer to enclosing class when enforcing @Restrict ------------------------------------------------- Key: JBSEAM-3192 URL: https://jira.jboss.org/jira/browse/JBSEAM-3192 Project: Seam Issue Type: Bug Components: Wicket Reporter: Pete Muir Fix For: 2.1.0.BETA2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3163) components.xml <property> parsing for sets

by Pete Muir (JIRA)

components.xml <property> parsing for sets ------------------------------------------ Key: JBSEAM-3163 URL: http://jira.jboss.com/jira/browse/JBSEAM-3163 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Assigned To: Norman Richards Priority: Critical Fix For: 2.1.0.BETA1 See the wiki tests for an example of this failing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3252) org.jboss.seam.core.Validators not JSF 1.1 compliant

by Richard Kennard (JIRA)

org.jboss.seam.core.Validators not JSF 1.1 compliant ---------------------------------------------------- Key: JBSEAM-3252 URL: https://jira.jboss.org/jira/browse/JBSEAM-3252 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1 Environment: Any Reporter: Richard Kennard Priority: Minor org.jboss.seam.core.Validators.validate() seems to work by: a) wrapping a custom ValidatingResolver over the existing ELContext b) calling setValue c) relying on setValue triggering ValidatingResolver.setValue d) ValidatingResolver.setValue calls Hibernate Validator This works fine if the ValueExpression is a com.sun.facelets.el.TagValueExpression, as created by Facelets or some other JSF 1.2 framework. However, if the ValueExpression is a javax.faces.component.ValueExpressionValueBindingAdapter (a compatibility wrapper from a JSF 1.1 component) then steps c) and d) do not happen: the value is set without going through ELContext or ValidatingResolver, and so passes successfully without ever being validated. Perhaps an earlier version of Seam used a JSF 1.1-based approach? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3249) Add bridge between Servlet Security and Identity component

by Dan Allen (JIRA)

Add bridge between Servlet Security and Identity component ---------------------------------------------------------- Key: JBSEAM-3249 URL: https://jira.jboss.org/jira/browse/JBSEAM-3249 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.0.3.CR2, 2.1.0.BETA1 Spring Security uses a security context integration filter that wraps the HttpServletRequest so that the security framework can respond to getUserPrincipal(), getRemoteUser(), and isUserInRole(). We should support this style of integration with our Identity component, especially since Seam prides itself on making standard Java EE stuff work. In fact, doing so is ridiculously easy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2684) #{entityQuery.dataModel} returns empty model

by Alex Savitsky (JIRA)

#{entityQuery.dataModel} returns empty model -------------------------------------------- Key: JBSEAM-2684 URL: http://jira.jboss.com/jira/browse/JBSEAM-2684 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Alex Savitsky Priority: Critical When referenced from a JSF dataTable, a dataModel property from a conversation-scoped EntityQuery ALWAYS returns an empty model. The resultList property works normally, though. Placing the EntityQuery in session scope works, too. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 5 months

4
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008