August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2607) ThreadPoolDispatcher: exceptions from AsynchronousInvocation.call() are not logged

by Adam Warski (JIRA)

ThreadPoolDispatcher: exceptions from AsynchronousInvocation.call() are not logged ---------------------------------------------------------------------------------- Key: JBSEAM-2607 URL: http://jira.jboss.com/jira/browse/JBSEAM-2607 Project: JBoss Seam Issue Type: Feature Request Components: Async Affects Versions: 2.0.1.GA Reporter: Adam Warski Priority: Minor When using a ThreadPoolDispatcher, if an asynchronous method is called, and the AsynchronousInvocation.call() method fails (for example because of an injected bean, which isn't yet created and doesn't have @AutoCreate), the exception is not logged anywhere, making it quite hard to debug. -- 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

17 years, 7 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3358) ant dist doesn't work in build distribution

by Pete Muir (JIRA)

ant dist doesn't work in build distribution ------------------------------------------- Key: JBSEAM-3358 URL: https://jira.jboss.org/jira/browse/JBSEAM-3358 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.1.0.BETA1 Reporter: Pete Muir Fix For: 2.1.0.CR1 -- 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

17 years, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3273) @Startup + @Create on session-scoped bean broken in Seam 2.1

by Przemyslaw Jaskierski (JIRA)

@Startup + @Create on session-scoped bean broken in Seam 2.1 ------------------------------------------------------------ Key: JBSEAM-3273 URL: https://jira.jboss.org/jira/browse/JBSEAM-3273 Project: Seam Issue Type: Bug Environment: clean Tomcat 6.0.16, Seam 2.1 build 281 Reporter: Przemyslaw Jaskierski Priority: Critical In 1.x, 2.x and Seam 2.1 build from ~march 2008 it was possible to access, for example, cookies info or other http request attributes at session creation time. It was extremely useful to fetch f.e. user-specific data from database to create custom view etc, (described f.e. here http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963032). It is not working anymore. Both FacesContext.getCurrentInstance() and ServletContexts.getInstance().getRequest() now return null within @Create method. @Name("sessionStateBacker") @Scope(ScopeType.SESSION) @Startup public class UserStateBacker implements Serializable { @Create public void sessionCreated() { FacesContext facesContext = FacesContext.getCurrentInstance(); if (facesContext == null) { System.out.println("FacesContext is null in 2.1.0 but worked fine in 2.0.3"); } //facesContext.getExternalContext().getRequestCookieMap(); } } -- 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

17 years, 7 months

3
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3348) StatusMessages discards all messages issued without a resource bundle key

by Stefano Travelli (JIRA)

StatusMessages discards all messages issued without a resource bundle key ------------------------------------------------------------------------- Key: JBSEAM-3348 URL: https://jira.jboss.org/jira/browse/JBSEAM-3348 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.BETA1 Environment: Ubuntu 8.04, JVM 1.6.0_06, JBoss 4.2.2 Reporter: Stefano Travelli This is a regression after JBSEAM-3318. StatusMessages.add(messageTemplate, params..) and StatusMessages.add(severity, messageTemplate, params..) delegate the message to add(severity, key, detailKey, messageTemplate, messageDetailTemplate, params..) with null for 'key'. However the code discards the message if key is null (or empty) so that no message is added. -- 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

17 years, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3360) EntityManager becoming detached in EntityConverter

by Pete Muir (JIRA)

EntityManager becoming detached in EntityConverter -------------------------------------------------- Key: JBSEAM-3360 URL: https://jira.jboss.org/jira/browse/JBSEAM-3360 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.0.BETA1 Reporter: Pete Muir Assignee: Pete Muir Fix For: 2.1.0.CR1 -- 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

17 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3357) NPE on hot deploy

by Pete Muir (JIRA)

NPE on hot deploy ----------------- Key: JBSEAM-3357 URL: https://jira.jboss.org/jira/browse/JBSEAM-3357 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.BETA1 Reporter: Pete Muir Assignee: Pete Muir Priority: Critical Fix For: 2.1.0.CR1 -- 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

17 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2594) Container issue - improved exception handling in Seam

by Shane Bryzak (JIRA)

Container issue - improved exception handling in Seam ----------------------------------------------------- Key: JBSEAM-2594 URL: http://jira.jboss.com/jira/browse/JBSEAM-2594 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Christian brought up a list of improvements that we can make to exception handling in Seam. This container issue will be used to group these items. -- 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

17 years, 7 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2714) Detect swallowed exceptions

by Matt Drees (JIRA)

Detect swallowed exceptions --------------------------- Key: JBSEAM-2714 URL: http://jira.jboss.com/jira/browse/JBSEAM-2714 Project: JBoss Seam Issue Type: Feature Request Components: Exception Handling Reporter: Matt Drees Priority: Minor Sometimes exceptions are swallowed by frameworks out of Seam's control (Facelets debug component, for example does this; see http://www.seamframework.org/Community/FetchingDataLazilyOnANewPage#comme...). However, a rollback may be triggered by the throwing of such an exception, due to the RollbackInterceptor. Because the exception is swallowed, the developer has no immediate indication that an error has occurred, yet the persistence context will be cleared. It's a very frustrating experience, trust me. Could Seam use an interceptor to note when a (non-application) exception is thrown by a Seam component, and if it is not eventually handled by Seam's exception handler at the end of the request, trigger a warning & a stacktrace in the log? -- 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

17 years, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2597) Exception handling - JSF swallows exceptions in certain phases

by Shane Bryzak (JIRA)

Exception handling - JSF swallows exceptions in certain phases -------------------------------------------------------------- Key: JBSEAM-2597 URL: http://jira.jboss.com/jira/browse/JBSEAM-2597 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA I can't reproduce this right now but I'm sure I spent several hours with a debugger only to find out that I had a typo in a value binding and that the exception was completely swallowed during an early JSF phase (UPDATE MODEL probably). There was nothing in the log, the action phase just never executed. This is a major issue (obviously) for another subtle reason: Beginners have trouble understanding the JSF lifecycle and processing phases - I know I did. You begin to hate JSf when you don't understand why a certain phase does not execute. I'd start reproducing it by generating an NPE in a value binding setter, that should do it. -- 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

17 years, 7 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1183) Allow custom ExceptionHandler implementations to be inserted

by Mike Quilleash (JIRA)

Allow custom ExceptionHandler implementations to be inserted ------------------------------------------------------------ Key: JBSEAM-1183 URL: http://jira.jboss.com/jira/browse/JBSEAM-1183 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Currently you can only configure a small subset of actions to occur on an exception (redirect, http-error etc). Enhancing the exception configuration xml to allow pluggable ExceptionHandler implementations would make this a lot more flexible. e.g. pages.xml <pages>  <exception class="javax.persistence.EntityNotFoundException"> <http-error error-code="404"/> </exception>  <exception handlerClass="com.xxx.seam.CustomExceptionHandler"/> </pages> These should probably have higher precedence than standard configure-by-exception-class handlers. -- 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

17 years, 7 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008