April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3740) ManagedHibernateSession not disconnected after rendering response

by Jakub Janczak (JIRA)

ManagedHibernateSession not disconnected after rendering response ----------------------------------------------------------------- Key: JBSEAM-3740 URL: https://jira.jboss.org/jira/browse/JBSEAM-3740 Project: Seam Issue Type: Task Components: Core Affects Versions: 2.0.2.SP1 Environment: jboss-4.2.3.ga Reporter: Jakub Janczak Priority: Optional It's not a bug, but it would be nice of Seam to close the connection of the hibernate session after rendering the page. It's crucial when hibernate is used in filters which are not using seam managed Session - especially for Jboss's CachedConnectionManager which is closing old jdbc connections before creating a new ones, causing a Seam managed session to disfunct. -- 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

15 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2257) Raise a session expired and new session event on occurence

by Jacob Orshalick (JIRA)

Raise a session expired and new session event on occurence ---------------------------------------------------------- Key: JBSEAM-2257 URL: http://jira.jboss.com/jira/browse/JBSEAM-2257 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 2.0.0.GA Reporter: Jacob Orshalick Priority: Minor You have to make some assumptions here, but you can basically notify the user when the server session has ended with the following in a PhaseListener: Code: @Observer("org.jboss.seam.beforePhase") public void beforePhase(PhaseEvent event) { if(event.getPhaseId() == PhaseId.RESTORE_VIEW) { HttpServletRequest request = (HttpServletRequest) FacesContext.getCurrentInstance() .getExternalContext().getRequest(); if(request.getRequestedSessionId() != null && request.getSession().isNew()) Events.instance().raiseEvent("org.jboss.seam.sessionExpired"); ... Based on general cookie settings this will raise the event when the user still has the browser window open, the http session expired, and the user tries to access the app. If the user closes and reopens the browser to start the application, the event will not be raised. This of course makes the assumption that cookies expire when the browser session is ended (which is generally the case). The org.jboss.seam.newSession event would simply change the condition to: if(request.getRequestedSessionId() == null && request.getSession().isNew()) Events.instance().raiseEvent("org.jboss.seam.newSession"); This is generally useful for user notification on the login screen. Please see the forum reference for more information. 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

15 years

5
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3583) Optimize EntityConverter

by Pete Muir (JIRA)

Optimize EntityConverter ------------------------ Key: JBSEAM-3583 URL: https://jira.jboss.org/jira/browse/JBSEAM-3583 Project: Seam Issue Type: Feature Request Components: JSF Controls Reporter: Pete Muir Fix For: 2.1.1.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

15 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2989) Log Seam FacesMessages with a filterable flag

by Pete Muir (JIRA)

Log Seam FacesMessages with a filterable flag --------------------------------------------- Key: JBSEAM-2989 URL: http://jira.jboss.com/jira/browse/JBSEAM-2989 Project: Seam Issue Type: Feature Request Components: JSF Integration Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.BETA1 Needed for support other view layers -- 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

15 years

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3331) Allow selective UI generation in seam-rev-eng.xml

by Valerie Griffin (JIRA)

Allow selective UI generation in seam-rev-eng.xml ------------------------------------------------- Key: JBSEAM-3331 URL: https://jira.jboss.org/jira/browse/JBSEAM-3331 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.3.CR1 Reporter: Valerie Griffin The seam-rev-eng.xml file allows hibernate to be told which entities are to be generated. There is no way to define the set of UI's to generate. It would also be convenient to be able to specify model or ui generation for one or more specified entities after the initial generation. -- 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

15 years

6
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3373) Support sending custom headers when an http error is sent

by Pete Muir (JIRA)

Support sending custom headers when an http error is sent --------------------------------------------------------- Key: JBSEAM-3373 URL: https://jira.jboss.org/jira/browse/JBSEAM-3373 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Fix For: 2.1.1.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

15 years

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3385) Destroying one conversation from within another

by Bernard Labno (JIRA)

Destroying one conversation from within another ----------------------------------------------- Key: JBSEAM-3385 URL: https://jira.jboss.org/jira/browse/JBSEAM-3385 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1 Environment: JBoss 4.2.3.GA Reporter: Bernard Labno There is a problem with destroying conversation via ConversationEntry.destroy(). In ConversationEntry : public void destroy() { boolean success = Manager.instance().switchConversation( getId() ); if (success) Manager.instance().endConversation(false); } After this method the conversation id is wrong ! We could have destroy one conversation from another and guess which conversation's id will appear if we try to render it ? The removed conversation's ! We just removed one conversation and got kicked out of another. -- 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

15 years

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3864) Document working with multiple seam-gen projects - JBSEAM-2338

by Jay Balunas (JIRA)

Document working with multiple seam-gen projects - JBSEAM-2338 -------------------------------------------------------------- Key: JBSEAM-3864 URL: https://jira.jboss.org/jira/browse/JBSEAM-3864 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Dan Allen Fix For: 2.1.2.CR1 Document how to use seam-gen to manage multiple projects - JBSEAM-2338 -- 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

15 years

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1978) Minimize the performance cost of calling getter in JBoss EL

by Mikhail Grushinskiy (JIRA)

Minimize the performance cost of calling getter in JBoss EL ----------------------------------------------------------- Key: JBSEAM-1978 URL: http://jira.jboss.com/jira/browse/JBSEAM-1978 Project: JBoss Seam Issue Type: Feature Request Reporter: Mikhail Grushinskiy Minimize the performance cost of calling getter in JBoss EL bean.property is the most common EL construct used in all JSF applications. The cost of calling property getter in EL is more important to overall JSF application performance (specifically rendering phase) See also http://jira.jboss.com/jira/browse/JBSEAM-1977 -- 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

15 years

6
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3205) Make it easier to get the delegate you want

by Pete Muir (JIRA)

Make it easier to get the delegate you want ------------------------------------------- Key: JBSEAM-3205 URL: https://jira.jboss.org/jira/browse/JBSEAM-3205 Project: Seam Issue Type: Feature Request Components: Core Reporter: Pete Muir Assignee: Christian Bauer Fix For: 2.1.0.BETA2 PersistenceProvider.instance.getDelegate(Class clazz) which returns the requested delegate (e.g. a FullTextSession) -- 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

15 years

5
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009