October 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4654) s:selectItems noSelectionLabel does not generate option value

by Andrew Wheeler (JIRA)

s:selectItems noSelectionLabel does not generate option value ------------------------------------------------------------- Key: JBSEAM-4654 URL: https://jira.jboss.org/browse/JBSEAM-4654 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.1.CR1 Environment: JBoss 6 M3 Reporter: Andrew Wheeler When a selectOneMenu has no items other than the no selection option it does not render the option value as org.jboss.seam.ui.NoSelectionConverter.noSelectionValue. In this case the there are no values in person.images. <h:selectOneMenu id="portrait" value="#{person.portrait}"> <s:selectItems value="#{person.images}" var="i" label="#{i.annotation}" hideNoSelectionLabel="false" noSelectionLabel="Select a portrait..."/> <s:convertEntity/> </h:selectOneMenu> This renders: <select id="person:portraitDecoration:portrait" name="person:portraitDecoration:portrait" size="1"> <option selected="selected">Select a portrait...</option> </select> The result is that any form submit causes a java.lang.NumberFormatException with message: "For input string: "Select a portrait..."" I have debugged a little and I can see that the converter is not firing when rendering the page. It does however fire for other selectOneMenu items on the page that have one or more items. A similar and perhaps related issue is referenced in the JBoss Forum. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

10
24
0 / 0

[JBoss JIRA] (JBSEAM-5051) messageList on place off messageManager - seam-reference-2.3.0.Final

by Luiz Augusto (JIRA)

Luiz Augusto created JBSEAM-5051: ------------------------------------ Summary: messageList on place off messageManager - seam-reference-2.3.0.Final Key: JBSEAM-5051 URL: https://issues.jboss.org/browse/JBSEAM-5051 Project: Seam 2 Issue Type: Patch Components: Documentation Issues Affects Versions: 2.3.0.Final Environment: Documentation Reporter: Luiz Augusto Priority: Critical Fix For: The future Type mismatch. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] (JBSEAM-4958) Improve the Seam UI javadoc

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-4958: ------------------------------------- Summary: Improve the Seam UI javadoc Key: JBSEAM-4958 URL: https://issues.jboss.org/browse/JBSEAM-4958 Project: Seam 2 Issue Type: Enhancement Components: JSF Controls Affects Versions: 2.3.0.BETA1, 2.3.0.BETA2 Reporter: Marek Novotny Assignee: Marek Novotny Fix For: 2.3.0.CR1 Improve documentation in Seam UI components at http://docs.jboss.org/seam/2.3.0.Beta2/ui/apidocs/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4529) org.jboss.seam.framework.Query --- count query generation fails if the query contains a JOIN FETCH operation written in uppercase

by Wolfgang Schwendt (JIRA)

org.jboss.seam.framework.Query --- count query generation fails if the query contains a JOIN FETCH operation written in uppercase ---------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4529 URL: https://jira.jboss.org/jira/browse/JBSEAM-4529 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: Seam 2.2.1 Rev 11984 Reporter: Wolfgang Schwendt Priority: Minor org.jboss.seam.framework.Query. The count query generation fails with an exception if the query contains a JOIN FETCH operation written in uppercase (rather than lowercase). -- 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

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4701) Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE

by Brian Dill (JIRA)

Cookie path being set to empty string via getRequestContextPath forming invalid cookies in IE --------------------------------------------------------------------------------------------- Key: JBSEAM-4701 URL: https://jira.jboss.org/browse/JBSEAM-4701 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Brian Dill When using <s:token /> in JSF the javax.faces.ClientToken cookie that is created can potentially have an empty ("") path which will cause it to not be accepted in some versions of Internet Explorer. The following code in ClientUidSelector is the problem. setCookiePath(FacesContext.getCurrentInstance().getExternalContext().getRequestContextPath()); This bug can be manifested as "viewId: /myPage.xhtml - No client identifier provided." I'll try to post a patch file here asap. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
14
0 / 0

[JBoss JIRA] (JBSEAM-5047) Transaction lookup fails on Tomcat

by Christoph Brill (JIRA)

Christoph Brill created JBSEAM-5047: --------------------------------------- Summary: Transaction lookup fails on Tomcat Key: JBSEAM-5047 URL: https://issues.jboss.org/browse/JBSEAM-5047 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.3.0.Final Reporter: Christoph Brill Currently org.jboss.seam.transaction.Transaction#getUserTransaction() catches for a NameNotFoundException when doing the lookup for "java:comp/UserTransaction". This fails on Apache Tomcat 7.0.27 because it will throw a generic NamingException. Please change the code to catch a NamingException instead of NameNotFoundException (which is a child class of NamingException). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4398) RememberMe Issue - Base 64 encoded cookie containing '=' is not processed correctly in some cases

by Peter Goldstein (JIRA)

RememberMe Issue - Base 64 encoded cookie containing '=' is not processed correctly in some cases ------------------------------------------------------------------------------------------------- Key: JBSEAM-4398 URL: https://jira.jboss.org/jira/browse/JBSEAM-4398 Project: Seam Issue Type: Bug Affects Versions: 2.2.0.GA, 2.1.2.GA Environment: Observed on Windows Vista, JBoss 5.1.0 GA. Problem likely exists on other operating systems and other Tomcat 6 based systems. Reporter: Peter Goldstein When attempting to use the RememberMe component in auto-login mode I discovered a bug in the cookie handling of this component. When attempting to log using an auth token I was encountering repeated failures - the token was simply not being found in the database. After some investigation I discovered that the problem was that the value parameter passed into the query was truncated by one character - the last character was cut off. I tracked the problem further back, and discovered that the truncated value originated in JBoss' Tomcat. The cookie value being passed in was missing the last two '=' characters. Some Google searching revealed that this was deliberate - Tomcat 6 in the JBoss 5.1.0 GA configuration enforces strict character rules in the cookie value, which excludes '='. I'm not sure if Tomcat 6 is 'right' or not, but I do know that either way, this is a trivial issue to address on the Seam side. All one has to do is replace the '=' from the Base64 encoded token value with another allowed character (say '_' or '-') before placing it in a cookie, and reverse the process when reading a cookie. I have a patch for this issue on the 2.2.0 GA code. I simply need to know how to submit it. -- 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

12 years, 3 months

8
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2012