October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1893) Default action for a JSF form

by Fernando Montaño (JIRA)

Default action for a JSF form ----------------------------- Key: JBSEAM-1893 URL: http://jira.jboss.com/jira/browse/JBSEAM-1893 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Fernando Montaño Enable the possibility to invoke some action (e.g. commandButton) when the user hits Enter key in a form. -- 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

17 years, 1 month

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2190) SeamScopePostProcessor should include defaultAutoCreate attribute

by Dan Allen (JIRA)

SeamScopePostProcessor should include defaultAutoCreate attribute ----------------------------------------------------------------- Key: JBSEAM-2190 URL: http://jira.jboss.com/jira/browse/JBSEAM-2190 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.CR3 Reporter: Dan Allen Assigned To: Michael Youngstrom Fix For: 2.0.1.GA In terms of the Seam-Spring bridge, the auto-create functionality is almost always desired. The default behavior for Seam-scoped Spring beans is to not register an auto-create variable. As a result, I find that I have to resort to using a nested <seam:component> simply to get auto-create functionality. I can understand that the setting has to be global (whether or not to register an auto-create variable in the SeamScopePostProcessor), but I feel it should at least be a switch that would appear on the <seam:configure-scopes> tag. -- 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

17 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2153) ConversationEntry.redirect applies page parameters

by Pete Muir (JIRA)

ConversationEntry.redirect applies page parameters -------------------------------------------------- Key: JBSEAM-2153 URL: http://jira.jboss.com/jira/browse/JBSEAM-2153 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Fix For: 2.0.1.GA ConversationEntry.redirect applies page parameters to the redirect. Thus state in the redirected-to conversation is overwritten by state in the redirected-from conversation when: 1) The page parameter's value exists in the redirected-from conversation 2) The redirected-to conversation's view applies a page parameter with the same name If (2) doesn't happen it doesn't cause the state to be overwritten but we still end up with an incorrect url. -- 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

17 years, 1 month

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2182) Add support for Seam component support for InitializingBean in the Spring integration

by Michael Youngstrom (JIRA)

Add support for Seam component support for InitializingBean in the Spring integration ------------------------------------------------------------------------------------- Key: JBSEAM-2182 URL: http://jira.jboss.com/jira/browse/JBSEAM-2182 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.CR3 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.1.GA Spring provides integrations with lots of 3rd party tools. It would be nice if Seam could take better advantage of these integrations without having to embed a Spring container. One way Seam can do this is provide an interceptor that looks for beans that implemented InitialziingBean and calls afterPropertiesSet(). -- 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

17 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2150) JSF can try to access it's messages bundle before Seam starts

by Pete Muir (JIRA)

JSF can try to access it's messages bundle before Seam starts ------------------------------------------------------------- Key: JBSEAM-2150 URL: http://jira.jboss.com/jira/browse/JBSEAM-2150 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Priority: Minor Fix For: 2.0.1.GA This causes an IllegalStateException as the contexts aren't active. We should deal with this case by just returning the key or using the delegate or 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

17 years, 1 month

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2055) NPE in UIComponent when ViewRoot not available

by Matt Drees (JIRA)

NPE in UIComponent when ViewRoot not available ---------------------------------------------- Key: JBSEAM-2055 URL: http://jira.jboss.com/jira/browse/JBSEAM-2055 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR1 Reporter: Matt Drees Priority: Minor I have an @Observer("org.jboss.seam.beforePhase") in a component that injects a UIComponent via #{uicomponent[...]} java.lang.NullPointerException at org.jboss.seam.faces.UiComponent$1.get(UiComponent.java:56) at org.jboss.seam.faces.UiComponent$1.get(UiComponent.java:45) at javax.el.MapELResolver.getValue(MapELResolver.java:51) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstBracketSuffix.getValue(AstBracketSuffix.java:59) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:112) at org.jboss.seam.Component.getValueToInject(Component.java:2126) at org.jboss.seam.Component.injectAttributes(Component.java:1599) at org.jboss.seam.Component.inject(Component.java:1417) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) ... at org.jboss.seam.Component.callComponentMethod(Component.java:2087) at org.jboss.seam.core.Events.raiseEvent(Events.java:83) at org.jboss.seam.jsf.SeamPhaseListener.raiseEventsBeforePhase(SeamPhaseListener.java:381) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:118) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) ... -- 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

17 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1421) Example of how to extend Identity with configuration

by Pete Muir (JIRA)

Example of how to extend Identity with configuration ---------------------------------------------------- Key: JBSEAM-1421 URL: http://jira.jboss.com/jira/browse/JBSEAM-1421 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Shane Bryzak Priority: Minor This seems to come up a lot on the forum -- 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

17 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1901) ConversationEntry.isDisplayable should also check that its not isRemoveAfterRedirect

by Chris Rudd (JIRA)

ConversationEntry.isDisplayable should also check that its not isRemoveAfterRedirect ------------------------------------------------------------------------------------ Key: JBSEAM-1901 URL: http://jira.jboss.com/jira/browse/JBSEAM-1901 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd I have a situation where temporary conversations that are promoted to long running (due to a redirect) for views with a valid description show up in the conversationList. If ConversationEntry.isDisplayable adds the contraint !isRemoveAfterRedirect() , then the issue does not appear. public boolean isDisplayable() { return !isEnded() && !isRemoveAfterRedirect() && getDescription()!=null; } NOTE: The particular instance this occurs in for me is due to a current limitation in seam. Currently there is no way to end the current conversation and start a new one (under a new conversation context) in the same request. For instance : Im in conversation id 5, I hit the "done" button, which I want to end the current conversation (and destroy that context), then redirect me toto the same view starting a new conversation. There use to be a "new" propagation mode, but that seems to be missing now. If you simply start a new conversation after the redirect, the current conversation (the one promoted due to the redirect, the same one you wanted to end) is just propagated along and contains all same state as before. This is not the desired affect, I want a NEW conversation that contains only new items So my "workaround" is to have the "done" out come end the conversation, redirect me to another action, that then redirects me to my final view with a propagation none. The "problem" is that the first conversation, is still out there waiting to be "continued" so that it can convert it back into a temporary (as its marked removeAfterRedirect). Since is a long running conv, it shows up in the conv list (which it should not as its not really a long running conversation). The conv is eventually pruned (due to conv timeout). <rule if-outcome="done"> <end-conversation/> <redirect>  <param name="actionOutcome" value="#{'edit'}"/> <param name="conversationPropagation" value="none"/> </redirect> </rule> <rule if-outcome="edit"> <begin-conversation join="true"/> </rule> -- 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

17 years, 2 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2185) s:selectItems performance issue with many combo-box items

by Stephan Bublava (JIRA)

s:selectItems performance issue with many combo-box items --------------------------------------------------------- Key: JBSEAM-2185 URL: http://jira.jboss.com/jira/browse/JBSEAM-2185 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR3 Reporter: Stephan Bublava Priority: Minor UISelectItems.asSelectItems() iterates over all combo box items and calls getLabel() and getDisabled() (usually value expressions) twice per entry: for (Object o : iterable) { initVar(o); selectItems.add(new javax.faces.model.SelectItem(o, getLabel() == null ? null : getLabel(), "", getDisabled() == null ? false : getDisabled())); destroyVar(); } Using local variables can make a noticeable difference, if there are many combo box items. -- 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

17 years, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2191) Include latest stable Drools realease with Seam2.0

by Juraj Holtak (JIRA)

Include latest stable Drools realease with Seam2.0 -------------------------------------------------- Key: JBSEAM-2191 URL: http://jira.jboss.com/jira/browse/JBSEAM-2191 Project: JBoss Seam Issue Type: Task Components: Drools Affects Versions: 2.0.0.CR3 Reporter: Juraj Holtak Please bundle the latest Drools binaries with Seam2.0 as they fix serious bugs. -- 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

17 years, 2 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2007