January 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-378) Add an infrastructure component for Accessing a JBoss mail session

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-378?page=all ] Gavin King closed JBSEAM-378. ----------------------------- Resolution: Out of Date We now have the new mail package. > Add an infrastructure component for Accessing a JBoss mail session > ------------------------------------------------------------------ > > Key: JBSEAM-378 > URL: http://jira.jboss.com/jira/browse/JBSEAM-378 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Bradley Smith > Priority: Minor > > Please add an infrastructure component for interacting with a javax.mail.session obtained from JNDI. > possible component name: > org.jboss.seam.core.mail -- 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-680) seam pdf should support h:outputText or provide the equivalent

by Norman Richards (JIRA)

seam pdf should support h:outputText or provide the equivalent -------------------------------------------------------------- Key: JBSEAM-680 URL: http://jira.jboss.com/jira/browse/JBSEAM-680 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards We need to be able to attach converters and other JSF things to 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

1
4
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.2.0.BETA1 (was: 1.1.5.GA) slip it *again*! > 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.2.0.BETA1 > > > 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.2.0.BETA1 (was: 1.1.5.GA) slip again > 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.2.0.BETA1 > > > 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

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-395) Alternate "dispatcher" strategies

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-395?page=all ] Gavin King updated JBSEAM-395: ------------------------------ Fix Version/s: 1.2.0.BETA1 (was: 1.1.5.GA) slipping again > Alternate "dispatcher" strategies > --------------------------------- > > Key: JBSEAM-395 > URL: http://jira.jboss.com/jira/browse/JBSEAM-395 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Affects Versions: 1.1.0.BETA1 > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.2.0.BETA1 > > > Currently, dispatch of asynchronous calls and events is done via the timer service. There are really good reasons to support other dispatching strategies such as quartz, jBPM, etc. This can be done simply by supporting @Asynchronous(dispatcher="#{name}"). -- 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-688) <end-conversation before-redirect="true"/>

by Gavin King (JIRA)

<end-conversation before-redirect="true"/> ------------------------------------------ Key: JBSEAM-688 URL: http://jira.jboss.com/jira/browse/JBSEAM-688 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.5.GA In both pages.xml and pageflow. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-670) Obsolete theme is not redirected to default and is invalid causing exceptions

by Bill Wallace (JIRA)

Obsolete theme is not redirected to default and is invalid causing exceptions ----------------------------------------------------------------------------- Key: JBSEAM-670 URL: http://jira.jboss.com/jira/browse/JBSEAM-670 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 1.1.0.GA Environment: Firefox 2.0, Java 1.6 running JBoss 4.0.5 Reporter: Bill Wallace If you create a theme, using cookies to store the theme, then remove that theme, or change the name, and go back to any page using the them in the template, an exception will be thrown with no indication as to why the data is unavailable. I had created themes named: default.theme and mobile.theme and then I removed the .theme portion of it. This caused the exception to be thrown. -- 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-621) Room rate support in jpa, glassfish, hibernate2 (and perhaps WLS / WAS EJB3) examples

by Michael Yuan (JIRA)

Room rate support in jpa, glassfish, hibernate2 (and perhaps WLS / WAS EJB3) examples ------------------------------------------------------------------------------------- Key: JBSEAM-621 URL: http://jira.jboss.com/jira/browse/JBSEAM-621 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Michael Yuan Fix For: 1.1.1.GA -- 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-686) Conversation cleanup does not work for a request that invaldiates the session

by Chris Rudd (JIRA)

Conversation cleanup does not work for a request that invaldiates the session ----------------------------------------------------------------------------- Key: JBSEAM-686 URL: http://jira.jboss.com/jira/browse/JBSEAM-686 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1 Reporter: Chris Rudd Priority: Minor If beans are added to a long running conversation in the same request that Seam.invalidateSession() is called, they will not be destroyed correctly. This is because the conversation is never flushed to the Session object, and therefore ServerConversationContext.getNamesFromSession() cannot see them. <LifeCycle: 308> if ( Contexts.isConversationContextActive() ) { if ( !Manager.instance().isLongRunningConversation() ) { log.debug("destroying conversation context"); Contexts.destroy( Contexts.getConversationContext() ); } if ( !Seam.isSessionInvalid() && !Init.instance().isClientSideConversations() ) { log.debug("flushing server-side conversation context"); Contexts.getConversationContext().flush(); } } This will also happen when a Temporary Conversation is changed to a long running because of a redirect (which is where i found the problem initially) and Seam.InvalidateSession() has been called. It seems that the !Seam.isSessionInvalid() check should be removed. The SeamListener when it sees the sessionDestroyed event will properly clean up the context. NOTE: If the bean was already in the conversation from a previous request (long running conversation only) then the issue does not occur as the object id already part of the sessions attributes from a previous request. -- 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
4
0 / 0

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

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-335?page=comments#action_12351472 ] Gavin King commented on JBSEAM-335: ----------------------------------- Yes, you need Seam 1.1. > 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

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