February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2545) Destroy session immediately on servlet request, if user is not logged in

by Christian Bauer (JIRA)

Destroy session immediately on servlet request, if user is not logged in ------------------------------------------------------------------------ Key: JBSEAM-2545 URL: http://jira.jboss.com/jira/browse/JBSEAM-2545 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer We can save some session memory by destroying the session at the end of a servlet request (FeedServlet, FileServlet), if the user is not logged in. That way we don't have to keep the session for 30 minutes after a feed poll. -- 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, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2626) Performing a second search from the Search Results

by Keith Naas (JIRA)

Performing a second search from the Search Results -------------------------------------------------- Key: JBSEAM-2626 URL: http://jira.jboss.com/jira/browse/JBSEAM-2626 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Environment: Firefox 2.0.0.12 Reporter: Keith Naas Assigned To: Christian Bauer Priority: Minor I ran a search to try to find a term. It displays the results. Then I change the search term at the top of the page. If I click the Find button it works perfectly. However, if I use the enter key it does not. Probably the Function for the "earchControlForm:searchControlSearchString" can also be applied to the Terms input field. -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2628) Display seamframework.org info about environment

by Keith Naas (JIRA)

Display seamframework.org info about environment ------------------------------------------------ Key: JBSEAM-2628 URL: http://jira.jboss.com/jira/browse/JBSEAM-2628 Project: JBoss Seam Issue Type: Feature Request Environment: Firefox 2.0.0.12 Reporter: Keith Naas Priority: Trivial At the bottom of the screen, or somewhere on seamframework.org it would be handy if information about the execution environment was available. For instance, version of Seam, JBoss, Java. The most important of which would be the Seam version so I can make sure I am making code changes to the right version :) -- 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, 11 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2599) Exception handling - Fix the JSF RI ViewExpiredException

by Shane Bryzak (JIRA)

Exception handling - Fix the JSF RI ViewExpiredException -------------------------------------------------------- Key: JBSEAM-2599 URL: http://jira.jboss.com/jira/browse/JBSEAM-2599 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA If you submit an h:form on a timed out session, you expect that exception - you need it to handle session timeout gracefully. I can not get the JSF RI to throw that exception even with a Hello World test, the form is processed on the new session without complaint - running into further problems because your state is not there. Probably involves writing a simple test case and submitting it to Sun. -- 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, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2596) Exception handling - Never try to do anything after an exception but exception handling

by Shane Bryzak (JIRA)

Exception handling - Never try to do anything after an exception but exception handling --------------------------------------------------------------------------------------- Key: JBSEAM-2596 URL: http://jira.jboss.com/jira/browse/JBSEAM-2596 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA This is related to JBSEAM-2595 Currently, if no exception handler is defined for an exception, Seam will (after logging and swallowing in SeamPhaseListener) happily continue with the next phase. It WILL fall over and blow up with another exception in almost all cases, especially if the rendering triggers any database access. These are the famous "Transaction is not active" exceptions that THEN will appear on the page. There is no hint of the real cause, the swallowed exception. Not even a "check in the log, idiot" message. We need to figure out if the default exception handler (without pages.xml) as proposed in 1. is sufficient to solve this issue. I'm not sure about RENDER RESPONSE 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, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2567) Javassist proxies aren't being correctly serialized

by Shane Bryzak (JIRA)

Javassist proxies aren't being correctly serialized --------------------------------------------------- Key: JBSEAM-2567 URL: http://jira.jboss.com/jira/browse/JBSEAM-2567 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.1.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 2.0.2.GA Stuff like this is appearing in the response packets for remoting quests: <ref id="52"><bean type="org.domain.remote.entity.Application_$$_javassist_67"><member name="applicationName"> This is definitely bad, and probably needs a similar workaround to what was done for cglib in BeanWrapper.serialize() -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2386) pages.xml redirect should accept plain URLs

by Christian Bauer (JIRA)

pages.xml redirect should accept plain URLs ------------------------------------------- Key: JBSEAM-2386 URL: http://jira.jboss.com/jira/browse/JBSEAM-2386 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor Instead of: <rule if-outcome="redirectToDocument"> <redirect view-id="/wiki.xhtml"> <param name="nodeId" value="#{documentHome.instance.id}"/> </redirect> </rule> I'd like to be able to do: <rule if-outcome="redirectToDocument"> <redirect url="#{wiki:renderURL(documentHome.instance)}"/> </rule> which would give me a nice URL without rewriting acrobatics. -- 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, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2291) Hot deploy pages.xml

by Pete Muir (JIRA)

Hot deploy pages.xml -------------------- Key: JBSEAM-2291 URL: http://jira.jboss.com/jira/browse/JBSEAM-2291 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.1.GA Ability to hot deploy pages.xml and *.page.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, 11 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1591) Redo ui example as a 'real life' example

by Pete Muir (JIRA)

Redo ui example as a 'real life' example ---------------------------------------- Key: JBSEAM-1591 URL: http://jira.jboss.com/jira/browse/JBSEAM-1591 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Lets have an example that has a purpose, rather than some mismash of control demonstrations. 80% of it is about a person and their interests, so lets build some sort of 'My Profile' app (very simple, no security etc.) - maybe a registration2 app? -- 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, 11 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1416) Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled

by Mike Quilleash (JIRA)

Make it clear in the documentation that Session scope concurrency is only handled when interception is enabled -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-1416 URL: http://jira.jboss.com/jira/browse/JBSEAM-1416 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash The concurrency section of the documentation says that seam automatically makes session scoped components threadsafe. Quote: Since the session context is multithreaded, and often contains volatile state, session scope components are always protected by Seam from concurrent access. However the implementation of this uses an interceptor so components that disable interception (InterceptionType.NEVER) will not benefit from this and threadsafety will have to be built into the component itself. This should be documented as the above states that they are ALWAYS protected. -- 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, 11 months

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