January 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-335) NullPointerException if user quikcly decides to click a different link or button before the page renders

by Karen Hundley (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-335?page=comments#action_12351471 ] Karen Hundley commented on JBSEAM-335: -------------------------------------- I am currently using the environment listed above and am getting this same error. The user clicks on a link then clicks another before the last one loads. This issue is listed as fixed and closed but I am wondering what I need to update to get this to work. Thanks! > NullPointerException if user quikcly decides to click a different link or button before the page renders > -------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-335 > URL: http://jira.jboss.com/jira/browse/JBSEAM-335 > Project: JBoss Seam > Issue Type: Bug > Components: JSF > Environment: Seam 1.0.1.GA. JBoss 4.0.4, Windows XP, Facelets, MyFaces, Hibernate > Reporter: Keith Naas > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.0.BETA1 > > > When a user is on one of our screens, they can decide to click a link before the next page loads. Sometimes, when this do this quickly enough, it causes a NullPointerException in Manager.touchConversationStack at line 181. Somehow, the currentConversationEntry is null and it breaks when it executes getCurrentConversationEntry().touch(). > I tried unsuccessfully to duplicate this scenario on the Hotel and DVD Store demos hosted on JBoss. > Stack Trace > java.lang.NullPointerException > at org.jboss.seam.core.Manager.touchConversationStack(Manager.java:181) > at org.jboss.seam.core.Manager.storeConversation(Manager.java:368) > at org.jboss.seam.jsf.AbstractSeamPhaseListener.storeAnyConversationContext(AbstractSeamPhaseListener.java:69) > at org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:45) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:578) > at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > ..... -- 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

19 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-684) Bug in documentation example section 3.6

by Christian Bauer (JIRA)

Bug in documentation example section 3.6 ---------------------------------------- Key: JBSEAM-684 URL: http://jira.jboss.com/jira/browse/JBSEAM-684 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.1.1.GA Reporter: Christian Bauer Priority: Trivial The first example in 3.6 extends AbstractMutable and calls setDirty() of that class, the second example also calls setDirty() but doesn't extend AbstractMutable. Looks like a copy/paste bug. -- 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

19 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-298) File uploads

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-298?page=all ] Gavin King closed JBSEAM-298. ----------------------------- Resolution: Duplicate Issue > File uploads > ------------ > > Key: JBSEAM-298 > URL: http://jira.jboss.com/jira/browse/JBSEAM-298 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > > Everyone seems to have trouble doing file uploads. Other web frameworks have integrated facilities for this - we should add something. -- 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

19 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-246) built-in component for handling files

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-246?page=all ] Gavin King closed JBSEAM-246. ----------------------------- Resolution: Duplicate Issue > built-in component for handling files > ------------------------------------- > > Key: JBSEAM-246 > URL: http://jira.jboss.com/jira/browse/JBSEAM-246 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > > It would be nice to have a built-in Seam component ManagedFile that lets me inject java.io.File object -- 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

19 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-663) jboss cache and redeploy

by Gavin King (JIRA)

jboss cache and redeploy ------------------------ Key: JBSEAM-663 URL: http://jira.jboss.com/jira/browse/JBSEAM-663 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.1.1.GA Reporter: Gavin King Assigned To: Norman Richards Fix For: 1.1.5.GA Use of s:cache in the blog example causes redeploy to fail. Let's find out exactly what causes this and fix 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

19 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-575) JSF views for PDF/HTML generation

by Gavin King (JIRA)

JSF views for PDF/HTML generation --------------------------------- Key: JBSEAM-575 URL: http://jira.jboss.com/jira/browse/JBSEAM-575 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Norman Richards Priority: Critical Fix For: 1.1.5.GA Wrap up iText in a bunch of JSF tags and possibly a special ViewHandler. -- 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

19 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-675) Improve Pages API; Add generic Page properties / meta-data

by Ryan Dewell (JIRA)

Improve Pages API; Add generic Page properties / meta-data ------------------------------------------------------------ Key: JBSEAM-675 URL: http://jira.jboss.com/jira/browse/JBSEAM-675 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Ryan Dewell Priority: Minor Ideas for getting the Page and Pages to be more useful to other parts of the application. Two ways to get there: ----- 1. Add a getAllPages() or getPages() to Pages.java. Just returns all of the Page definitions / objects that are defined for the current web-app. 2. Generic Page-level properties or attributes: <page....> <property name="Type" value="UsedFor"/> </page> Then accessing that from a Page object obtained from Pages: String value = page.getProperty(String name) ----------- With these two additions, elsewhere in my application I could now 1) iterate over all of the defined Page's using getPages(), 2) figure out which Page has a property of a given value 3) now know the view-id to construct a URL for. Basically using it to look up a view id in an application controlled way. This is one use case, but maybe there are more that would benefit from these 2 additions. -- 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

19 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-667) s:message does show up when ajax type validation is used

by Dan Liu (JIRA)

s:message does show up when ajax type validation is used -------------------------------------------------------- Key: JBSEAM-667 URL: http://jira.jboss.com/jira/browse/JBSEAM-667 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.1.GA Reporter: Dan Liu Priority: Minor I've tried the ajax validation example described in http://docs.jboss.com/seam/1.1GA/reference/en/html_single/#validation, but it doesn't work. If I change s:message to h:messages, it then works. -- 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

19 years, 2 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-116) Pluggable conversationId handler

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-116?page=all ] Gavin King updated JBSEAM-116: ------------------------------ Fix Version/s: 1.1.5.GA (was: 1.1.1.GA) > Pluggable conversationId handler > -------------------------------- > > Key: JBSEAM-116 > URL: http://jira.jboss.com/jira/browse/JBSEAM-116 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Priority: Critical > Fix For: 1.1.5.GA > > > Currently, there is no way to plug in a user-defined strategy for decoding and encoding the conversationId in the request/response. > We need this to really properly support AJAX/Soap invocations. -- 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

19 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-408) actionListener="#{foo.bar}" where bar() has no ActionEvent parameter

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-408?page=all ] Gavin King updated JBSEAM-408: ------------------------------ Fix Version/s: 1.1.5.GA (was: 1.1.1.GA) > actionListener="#{foo.bar}" where bar() has no ActionEvent parameter > -------------------------------------------------------------------- > > Key: JBSEAM-408 > URL: http://jira.jboss.com/jira/browse/JBSEAM-408 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1.5.GA > > > I hate the useless ActionEvent polluting my business code. I already fixed this in facelets, need a solution for JSP also. -- 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

19 years, 2 months

1
0
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 January 2007