February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2404) TimeZoneSelector: Initialization

by Martin Trummer (JIRA)

TimeZoneSelector: Initialization -------------------------------- Key: JBSEAM-2404 URL: http://jira.jboss.com/jira/browse/JBSEAM-2404 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.CR2 Reporter: Martin Trummer org.jboss.seam.international.TimeZoneSelector when called for the first time (no cookie set), initTimeZone() will not initialize the id, thus: * getTimeZoneId() will return null, but * getTimeZone() will return the default timezone this is not consistent it would be better to initialize the id in the initTimeZone() method to the default timezone (if no cookie is set). then the getTimeZone() method could always return java.util.TimeZone.getTimeZone( getTimeZoneId(), and another benefit is, that the null check in getTimeZone() can now be eliminated. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2189) ServletContexts.getInstance().getRequest() is null

by Menashe (JIRA)

ServletContexts.getInstance().getRequest() is null -------------------------------------------------- Key: JBSEAM-2189 URL: http://jira.jboss.com/jira/browse/JBSEAM-2189 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR3 Environment: jboss 4.2.2 sun jdk 1.5.0.13/1.6.0.3 started from jbosstool 2b4 Reporter: Menashe ServletContexts.getInstance().getRequest() is null when i try to access it from a seam bean -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1979) wrong default class for mssql in seam-gen : set as com.microsoft.sqlserver.jdbc.SQLServerDriver instead of com.microsoft.jdbc.sqlserver.SQLServerDriver

by thierry accart (JIRA)

wrong default class for mssql in seam-gen : set as com.microsoft.sqlserver.jdbc.SQLServerDriver instead of com.microsoft.jdbc.sqlserver.SQLServerDriver ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1979 URL: http://jira.jboss.com/jira/browse/JBSEAM-1979 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: seam-gen build.xml Reporter: thierry accart The build.xml for seam-gen contains a wrong default class for MSSQL driver : it's set with <condition property="hibernate.connection.driver_class.default" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"> <equals arg1="${database.type.new}" arg2="mssql"/> </condition> but the class for miscrosoft sql server is com.microsoft.jdbc.sqlserver.SQLServerDriver -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2195) Converters should be created in stateless scope

by Adam Warski (JIRA)

Converters should be created in stateless scope ----------------------------------------------- Key: JBSEAM-2195 URL: http://jira.jboss.com/jira/browse/JBSEAM-2195 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR3 Reporter: Adam Warski Priority: Minor Now, the converter scope is event, however it should be stateless, so that multiple usages of one converter on a page would work, in conjuction with facelets converter tags. For more details, see the forum. Also, what about validators? -- 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, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1532) include jar-versions.xml file

by Dan Allen (JIRA)

include jar-versions.xml file ----------------------------- Key: JBSEAM-1532 URL: http://jira.jboss.com/jira/browse/JBSEAM-1532 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.3.0.ALPHA Environment: seam CVS HEAD Reporter: Dan Allen Priority: Minor It would be so helpful if a jar-versions.xml file could be kept up to date in the root of the seam source code to track the versions of the bundle libraries, in the absence of other solutions. This idea comes from the JBoss AS, which uses this file to communicate the versions of libraries used. Documenting the versions helps: 1. developers, who may find challenge in combining APIs of libraries without knowing the version 2. users who are unable to determine the contents of what they downloaded 3. for legal reasons, just in case there are differences in licenses amongst releases of third party products, to protect seam itself as well as integrators of seam. With all that said, the better solution is to use ant-ivy or maven2 to get the jar files out of the source code. But I digress. -- 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, 11 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2227) Write some docs on how to use SeamTest without TestNG

by Dmitriy Lapko (JIRA)

Write some docs on how to use SeamTest without TestNG ----------------------------------------------------- Key: JBSEAM-2227 URL: http://jira.jboss.com/jira/browse/JBSEAM-2227 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.0.GA Reporter: Dmitriy Lapko -- 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, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2566) Interpolator cannot handle ##{expr}

by Norman Richards (JIRA)

Interpolator cannot handle ##{expr} ----------------------------------- Key: JBSEAM-2566 URL: http://jira.jboss.com/jira/browse/JBSEAM-2566 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Fix For: 2.0.2.GA -- 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, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2505) ServletContexts instance returns null request during JSF request

by Jacob Orshalick (JIRA)

ServletContexts instance returns null request during JSF request ---------------------------------------------------------------- Key: JBSEAM-2505 URL: http://jira.jboss.com/jira/browse/JBSEAM-2505 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick The ServletContexts.instance().getRequest() currently returns null during a JSF request. I would think this should be returning the external context for a JSF request. Remoting handlers, ContextualHttpServletRequest, and the SoapRequestHandler all set the HttpServletRequest into the ServletContexts instance. I have applied a patch in the FacesLifecycle.beginRequest() and it does the trick. I would be happy to submit the patch if you agree. Thanks. -- 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, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2507) javax.faces.application.ApplicationFactory exception when send a email from ActionHandler

by Stefano Zaccaria (JIRA)

javax.faces.application.ApplicationFactory exception when send a email from ActionHandler ----------------------------------------------------------------------------------------- Key: JBSEAM-2507 URL: http://jira.jboss.com/jira/browse/JBSEAM-2507 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.GA Environment: Windows vista, JBOSS AS 4.2.2GA, Seam 2.0.0GA Reporter: Stefano Zaccaria Fix For: 2.0.1.GA When send a e-mail from ActionHandler I recived a javax.faces.application.ApplicationFactory exception -- 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, 11 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2565) Using rich:listShuttle for N*N relations in UI

by thierry accart (JIRA)

Using rich:listShuttle for N*N relations in UI ---------------------------------------------- Key: JBSEAM-2565 URL: http://jira.jboss.com/jira/browse/JBSEAM-2565 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Environment: Seam 2.0.1+ (integrating rich faces 3.1.3+) Reporter: thierry accart A weak point in SEAM is the automatic generation of N-N CRUD pages With RichFaces 3.1.3, the listShuttle could allow easy CRUDing in N-N relations (and also or in 1-N relations). Maybe can someone find time to update the seam-gen templates and drive it to an higher level of user experience ? :) -- 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, 11 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008