February 2008 - seam-issues - Jboss List Archives

[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

16 years, 4 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

16 years, 4 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2600) Exception handling - Fix the exception handling in Seam

by Shane Bryzak (JIRA)

Exception handling - Fix the exception handling in Seam ------------------------------------------------------- Key: JBSEAM-2600 URL: http://jira.jboss.com/jira/browse/JBSEAM-2600 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Currently we have at least one serious race condition in our pages.xml exception handling, related to redirect/message passing. I can reproduce (JIRA case is open) lost messages on exception redirect. Also, clean up the #{exception} and #{handledException} stuff - which might fix the issue as a side effect. I want one exception instance I can access in EL, not two. I want to be able to call getRootCause() on it to unwrap the root exception. Of course the root cause is the one I specify in pages.xml as the one that is handled, but the #{exception} should always be the wrapper. In any case, a clear and reliable (working in all situations) strategy needs to apply here. -- 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, 4 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2595) Exception handling - Never swallow an exception

by Shane Bryzak (JIRA)

Exception handling - Never swallow an exception ----------------------------------------------- Key: JBSEAM-2595 URL: http://jira.jboss.com/jira/browse/JBSEAM-2595 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA For example, if an action throws NPE, the exception handler checks what is defined in pages.xml. If no handler is defined, SeamPhaseListener swallows the exception after printing it in the log. This is a bad strategy, as most users start with no exception handling defined and no pages.xml, yet they don't see their exceptions on the page. We need SOME default handler, even if no pages.xml is present. -- 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, 4 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2522) Update to JBoss Cache 2.1

by Pete Muir (JIRA)

Update to JBoss Cache 2.1 ------------------------- Key: JBSEAM-2522 URL: http://jira.jboss.com/jira/browse/JBSEAM-2522 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.GA This should sort out our dependencies a bit I hope. -- 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, 4 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2508) openId support components

by koen handekyn (JIRA)

openId support components ------------------------- Key: JBSEAM-2508 URL: http://jira.jboss.com/jira/browse/JBSEAM-2508 Project: JBoss Seam Issue Type: Feature Request Reporter: koen handekyn Priority: Optional provide standard components to allow easy setup for openId support in a seam application. the seam identity contains both username and password fields. an openId identity consist soly of an identity string. ideally an openId authenticator takes in just a single openId identity, performs the openId logn procedures and concludes (in case of succesful authentication in a logged in session, with the identifier confirmed. -- 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, 4 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1891) Decouple page fragment caching from JBoss Cache

by Christian Bauer (JIRA)

Decouple page fragment caching from JBoss Cache ----------------------------------------------- Key: JBSEAM-1891 URL: http://jira.jboss.com/jira/browse/JBSEAM-1891 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Minor The code in UICache and PojoCache only works with this component: return (org.jboss.cache.aop.PojoCache) Component.getInstance(PojoCache.class, ScopeType.APPLICATION); Make this generic so that other cache providers can be used. -- 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, 4 months

6
18
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

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1485) Configure Default Interceptors

by Bruno E. Grossi (JIRA)

Configure Default Interceptors ------------------------------ Key: JBSEAM-1485 URL: http://jira.jboss.com/jira/browse/JBSEAM-1485 Project: JBoss Seam Issue Type: Feature Request Components: Core Environment: Linux with only Tomcat, not JBoss Reporter: Bruno E. Grossi Create an configuration option to disable some default interceptors that there are never used, improving the application's performance. On some systems there are no necessity of some interceptors, for example, the transactional ones (RollbackInterceptor, TransactionInterceptor and ManagedEntityIdentityInterceptor) that degrade performance. -- 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-2432) Wildcard view-id descriptions for conversation switcher

by Jacob Orshalick (JIRA)

Wildcard view-id descriptions for conversation switcher ------------------------------------------------------- Key: JBSEAM-2432 URL: http://jira.jboss.com/jira/browse/JBSEAM-2432 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick Priority: Minor I have recently run into a requirement where it would be nice to have descriptions applied to wildcard view-ids. For example, if I have the following: Code: ... <page view-id="/section/*" conversation-required="true"> <description>Section 1</description> ... </page> ... Section 1 would be the description for all pages in /section/* unless specified otherwise in a higher precedence page definition. -- 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
6
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