November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1649) Run Seam filter stack with SeamTest

by Christian Bauer (JIRA)

Run Seam filter stack with SeamTest ----------------------------------- Key: JBSEAM-1649 URL: http://jira.jboss.com/jira/browse/JBSEAM-1649 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Reporter: Christian Bauer Priority: Minor I'd like to test my servlet filter with SeamTest. I've wrapped it as a Seam component and it is part of the regular Seam filter stack (within A4JSF filter). I don't think this is currently supported at all, the Seam filter doesn't run for FacesRequest/NonFacesRequest. I guess this would also enable testing of exceptions. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1642) It is difficult to call method on "outer" instance of component

by Michael Youngstrom (JIRA)

It is difficult to call method on "outer" instance of component --------------------------------------------------------------- Key: JBSEAM-1642 URL: http://jira.jboss.com/jira/browse/JBSEAM-1642 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Michael Youngstrom There may be cases were you are executing method in a component and you wish to call another method in the same component that executes the interceptors of that component. This is currently not really possible unless you explicitly grab the current instance of the component out of the scope it resides in. It would be nice if there were an easier way to achieve this. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-571) Custom Exception Handler

by Jye Tucker (JIRA)

Custom Exception Handler ------------------------ Key: JBSEAM-571 URL: http://jira.jboss.com/jira/browse/JBSEAM-571 Project: JBoss Seam Issue Type: Feature Request Components: Framework Reporter: Jye Tucker Ability to specify custom exception handlers through the exceptions component of the framework. -- 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, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1033) Allow programmatic adding of exception handlers

by Mike Quilleash (JIRA)

Allow programmatic adding of exception handlers ----------------------------------------------- Key: JBSEAM-1033 URL: http://jira.jboss.com/jira/browse/JBSEAM-1033 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Allow something like: Exceptions.instance().addHandler( exceptionHandler ); -- 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, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1765) Exception Handler without redirect

by Moshe Immerman (JIRA)

Exception Handler without redirect ---------------------------------- Key: JBSEAM-1765 URL: http://jira.jboss.com/jira/browse/JBSEAM-1765 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.0.BETA1 Reporter: Moshe Immerman Attachments: ActionErrorHandler.java, Exceptions.java.patch, pages-1.2.dtd.patch -- 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, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1597) Initialize jBPM when process-definitions are not configured in components.xml

by Piotr Walczyszyn (JIRA)

Initialize jBPM when process-definitions are not configured in components.xml ----------------------------------------------------------------------------- Key: JBSEAM-1597 URL: http://jira.jboss.com/jira/browse/JBSEAM-1597 Project: JBoss Seam Issue Type: Feature Request Components: BPM Environment: JBoss-4.2.0, Seam-2.0.BETA1 Reporter: Piotr Walczyszyn Priority: Minor I have a case where I use jBPM but I want to load processdefinitions myself, through jBPM api. When I have it configured in components.xml without any processdefinition entries just <bpm:jbpm/> it doesn't get fully loaded (hibernate mappings are not loaded etc). I would expect that jBPM gets fully loaded and configured when I just put <bpm:jbpm/> in componets.xml. -- 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, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1556) Multiple instances of Seam PhaseListener permitted to be registered in JSF lifecycle

by Neil Griffin (JIRA)

Multiple instances of Seam PhaseListener permitted to be registered in JSF lifecycle ------------------------------------------------------------------------------------ Key: JBSEAM-1556 URL: http://jira.jboss.com/jira/browse/JBSEAM-1556 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: WinXP / Liferay 4.3.0 / Tomcat 6.0.13 Reporter: Neil Griffin Background: I found this problem when trying to package-up the Seam "Registration" example as a portlet under Liferay Portal. The AbstractSeamPhaseListener class has a nice warning in the constructor, which alerts you in case more than one Seam-related PhaseListener is registered in the JSF lifecycle: private static boolean exists = false; protected AbstractSeamPhaseListener() { if (exists) log.warn("There should only be one Seam phase listener per application"); exists=true; } While this is good and helpful, the code needs to be improved to ENSURE that only one Seam-related PhaseListener is permitted to execute. Case in point: When running in a portlet environment and using MyFaces, JSF PhaseListeners get registered TWICE, due to the way MyFaces initializes itself: 1. MyFaces has a StartupServletContextListener that initializes the JSF framework (the first time). 2. The MyFacesGenericPortlet.initMyFaces() method initializes the JSF framework (a second time). Normally this would not be a big deal, but Seam has a restriction such that only one Seam-related PhaseListener may be active in the JSF Lifecycle. Because of the double-initialization that MyFaces is performing in the portlet scenario, any <phase-listener> elements found in the faces-config.xml file get registered twice! In Seam, this can cause all kinds of runtime problems. There are two ways that I can think of to fix this: 1. Only let the first PhaseListener "win", and prevent any others from executing their phase handler callbacks (even though registered in the JSF lifecycle). 2. Unregister PhaseListeners that don't win. This is hard to do though -- it can't be done in the constructor, because the PhaseListener can't unregister itself at that time, because it hasn't been added to the lifecycle yet. 2. -- 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, 10 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1474) Add examples with use of Facelets source tags

by Mikhail Grushinskiy (JIRA)

Add examples with use of Facelets source tags --------------------------------------------- Key: JBSEAM-1474 URL: http://jira.jboss.com/jira/browse/JBSEAM-1474 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 1.3.0.BETA1, 1.3.0.BETA2, 1.3.0.GA, 1.3.1.GA Reporter: Mikhail Grushinskiy Add examples with use of Facelets source tags. I think Facelets source tags is very useful feature which has to be demonstrated in examples provided with Seam -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1406) Create method to end/destroy other conversations

by Bruno E. Grossi (JIRA)

Create method to end/destroy other conversations ------------------------------------------------ Key: JBSEAM-1406 URL: http://jira.jboss.com/jira/browse/JBSEAM-1406 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Bruno E. Grossi In some situations we need to end/destroy other conversations different from the actual one. Manager has a private method Manager.destroyConversation(String conversationId, ContextAdaptor session) that can do it, but it private and requires a session ContextAdaptor. My suggestion to create a public method on Manager (or some other appropriate class) that receives an id the clean up that conversation. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1394) Null @Out attributes for stateless bean before/after method invocations

by H K (JIRA)

Null @Out attributes for stateless bean before/after method invocations ----------------------------------------------------------------------- Key: JBSEAM-1394 URL: http://jira.jboss.com/jira/browse/JBSEAM-1394 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: H K Priority: Optional Adding the ability to null @Out attributes for stateless session beans before/after method invocations should eliminate the chances of sharing the @Out instance variables when the stateless bean is being reused by the EJB container. Perhaps the tricky part here might be dealing with exceptions thrown by the intercepted methods. A possible solution might be to null the @Out attributes not only after the invocation but also before the invocation. Of course, this should be done only for stateless session 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, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007