September 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2717) Tomcat Integration reference guide chapter

by Jay Balunas (JIRA)

Tomcat Integration reference guide chapter ------------------------------------------ Key: JBSEAM-2717 URL: http://jira.jboss.com/jira/browse/JBSEAM-2717 Project: JBoss Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Following the existing interop reference guide chapters create a tomcat integration chapter. This chapter will cover deployments and limitations with and without JBoss embedded. There is already some information on tomcat deployment in the reference guide but it needs to be cleaned up with this single chapter. Likely version: tomcat 6.X References: http://tomcat.apache.org/ http://techieexchange.wordpress.com/2007/11/11/rad-seam-development-with-... http://www.jroller.com/wesleyhales/entry/running_seam_2_0_on http://www.michaelyuan.com/blog/2007/07/24/seam-20-and-tomcat/ http://jira.nuxeo.org/browse/NXP-1160 -- 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, 3 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3406) Back button in nested conversations

by Pablo Caballero (JIRA)

Back button in nested conversations ----------------------------------- Key: JBSEAM-3406 URL: https://jira.jboss.org/jira/browse/JBSEAM-3406 Project: Seam Issue Type: Bug Affects Versions: 2.0.3.CR1 Environment: Linux, jboss-4.2.2.GA Reporter: Pablo Caballero Pressing the back button after closing a nested conversation does not propagate to the parent conversation and creates a new conversation. For Example (see attached example files) Start parent conversation view id first.xhtml (let say conversation Id is 2) Start nested conversation view id second.xhtml (conversation Id is 3) Close nested conversation and redirect to first.xhtml (conversation id 2) Press the back button to try to view second.xhtml. Since the nested conversation is closed and no-conversation-view-id="/first.xhtml", the view stays in first.xhtml. However, a new conversation has been created with id 5. Conversation 2 is still active but in the background. (I Tried using natural conversations, but I believe nested and natural are not supported at this time) -- 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

16 years, 3 months

3
3
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

16 years, 3 months

5
24
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

16 years, 3 months

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

16 years, 3 months

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

16 years, 3 months

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

16 years, 3 months

4
4
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

16 years, 3 months

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

16 years, 3 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1875) Rework configuration chapter

by Pete Muir (JIRA)

Rework configuration chapter ---------------------------- Key: JBSEAM-1875 URL: http://jira.jboss.com/jira/browse/JBSEAM-1875 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Fix For: 2.0.0.GA Rework configuration chapter to make it a generic discussion of configuring and packaging Seam applications. Move platform specific stuff to platform specific chapter. i.e. 25 Configuring & Packaging Seam Applications 25.1 Basic Seam Configuration 25.1.1 Integrating Seam with JSF and the Servlet Container 25.1.2 Using Facelets 25.1.3 Seam Resource Servlet 25.1.4 Seam Filter 25.1.5. Integrating Seam with your EJB container 25.2 Seam Applications in a JEE 5 environment 25.3 Seam Applications in a J2EE environment 25.4 Seam Applicaitons in a JSE environment * Move JBPM configuration to JBPM chapter * Move JBoss AS stuff to new JBoss AS chapter * Move JBoss Embedded stuff to new JBoss Embedded Chapter 26 Seam on JBoss AS 26.1 Seam on JBoss AS 4.0 * Includes stuff on install JSF 1.2 from Chapter 2 26.2 Seam on JBoss AS 4.2 27 Seam with JBoss Embedded 28 Seam on OC4J 29 Seam on Glassfish * Needs writing! -- 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, 3 months

4
8
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 September 2008