August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Reopened: (JBSEAM-310) Global setting for no-conversation-view-id

by Christian Bauer (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-310?page=all ] Christian Bauer reopened JBSEAM-310: ------------------------------------ This is missing documentation, as well as the conversation-required="true" setting on a <page>. My experiments show that these are working together? > Global setting for no-conversation-view-id > ------------------------------------------ > > Key: JBSEAM-310 > URL: http://jira.jboss.com/jira/browse/JBSEAM-310 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1.0.BETA1 > > > Currently, no-conversation-view-id is too fine grained. We should allow a global setting to be used as the default if none is defined in pages.xml or the pageflow. > We also need no-conversation-view-id at pageflow level as well as node level. Cannot implement this w/o changes to jBPM. -- 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

18 years, 7 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1821) util.Work class does not properly handle java.lang.Errors when they are thrown

by Chris Rudd (JIRA)

util.Work class does not properly handle java.lang.Errors when they are thrown ------------------------------------------------------------------------------ Key: JBSEAM-1821 URL: http://jira.jboss.com/jira/browse/JBSEAM-1821 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd The util.Work class that manages transactions does not properly handle the case where a java.lang.Error is thrown. When a java.lang.Error is thrown the transaction is not properly cleaned up, due to the catch block only catching Exceptions. Please add the following additional catch block : Work.javal line 55 catch( Error e ) { if( begin ) { log.debug("rolling back transaction"); userTransaction.rollback(); } throw e; } -- 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

18 years, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1815) Upgrade HSQL lib for seam-gen to 1.8.0.7

by Christian Bauer (JIRA)

Upgrade HSQL lib for seam-gen to 1.8.0.7 ---------------------------------------- Key: JBSEAM-1815 URL: http://jira.jboss.com/jira/browse/JBSEAM-1815 Project: JBoss Seam Issue Type: Task Reporter: Christian Bauer Priority: Minor Fix For: 2.0.0.CR1 I've upgraded the hsqldb.jar in seam-gen/lib/ to HSQL DB 1.8.0.7 because I need a bugfix for GROUP BY with functions. The version that was previously in seam-gen/lib/ is unknown as someone killed the META-INF/MANIFEST.MF in that file with some generic JBoss crap. It was probably an earlier 1.8.x version so an upgrade should not be a problem. -- 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

18 years, 7 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1819) Use GNU Trove fast collections in Seam

by Mikhail Grushinskiy (JIRA)

Use GNU Trove fast collections in Seam -------------------------------------- Key: JBSEAM-1819 URL: http://jira.jboss.com/jira/browse/JBSEAM-1819 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Mikhail Grushinskiy Use GNU Trove fast collections in Seam for better performance http://trove4j.sourceforge.net/ -- 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

18 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1820) unique=true attribute of primary key in generated class prevents the schema to be regenerated

by Ali Sadik Kumlali (JIRA)

unique=true attribute of primary key in generated class prevents the schema to be regenerated --------------------------------------------------------------------------------------------- Key: JBSEAM-1820 URL: http://jira.jboss.com/jira/browse/JBSEAM-1820 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.BETA1 Environment: OS: Windows Vista 6.0,x86 Database: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc. Seam: jboss-seam-2.0.0.BETA1 Reporter: Ali Sadik Kumlali Priority: Trivial Following steps causes - Create a table using following script: CREATE TABLE PEOPLE ("ID" NUMBER NOT NULL, "SURNAME" VARCHAR2(50 BYTE), "NAME" VARCHAR2(25 BYTE), CONSTRAINT "PEOPLE_PK" PRIMARY KEY ("ID")); - Use seam generate-entities - Annotation of primary key column(ID) found in People.java should have "unique = true" attribute: @Id @Column(name = "ID", unique = true, nullable = false, precision = 22, scale = 0) @NotNull public BigDecimal getId() { return this.id; } - Drop the PEOPLE table: DROP TABLE "PEOPLE" CASCADE CONSTRAINTS; - To force the schema generated from entity class, redeploy application: seam deploy -- 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

18 years, 7 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1804) Page context instance not recognized in SeamTest

by Christian Bauer (JIRA)

Page context instance not recognized in SeamTest ------------------------------------------------ Key: JBSEAM-1804 URL: http://jira.jboss.com/jira/browse/JBSEAM-1804 Project: JBoss Seam Issue Type: Bug Components: Test Harness Reporter: Christian Bauer I didn't try CVS yet, this is 3 weeks old CVS. The issue with the following test is that 'beanB' is instantiated again on every call, be it a Component.getInstance() lookup or an Event that is fired. The goal of the test is to modify a value in BeanA and then get this new value into BeanB through a chain of events. @Name("beanA") @Scope(ScopeType.CONVERSATION) @AutoCreate public class BeanA { private String myValue; public String getMyValue() { return myValue; } public void setMyValue(String myValue) { this.myValue = myValue; } @Create public void create() { myValue = "Foo"; } @Observer(value = "BeanA.refreshMyValue") public void refreshMyValue() { myValue = "Bar"; Events.instance().raiseEvent("BeanA.valueModified"); } } @Name("beanB") @Scope(ScopeType.PAGE) @AutoCreate public class BeanB implements Serializable { private String myValue; public String getMyValue() { return myValue; } public void setMyValue(String myValue) { this.myValue = myValue; } @Observer(value = "BeanA.valueModified") public void takeValueFromBeanA() { BeanA beanA = (BeanA) Component.getInstance("beanA"); myValue = beanA.getMyValue(); } } public class MiscTests extends SeamTest { @Test public void eventChain() throws Exception { new FacesRequest("/docDisplay.xhtml") { protected void invokeApplication() throws Exception { BeanA beanA = (BeanA) Component.getInstance("beanA"); BeanB beanB = (BeanB) Component.getInstance("beanB"); assert "Foo".equals(beanA.getMyValue()); assert beanB.getMyValue() == null; Events.instance().raiseEvent("BeanA.refreshMyValue"); beanA = (BeanA) Component.getInstance("beanA"); beanB = (BeanB) Component.getInstance("beanB"); assert "Bar".equals(beanA.getMyValue()); assert "Bar".equals(beanB.getMyValue()); } }.run(); } } -- 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

18 years, 7 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1807) <s:attribute name="#{expr}" value="#{expr4value}" rendered="#{condition}"/>

by Mikhail Grushinskiy (JIRA)

<s:attribute name="#{expr}" value="#{expr4value}" rendered="#{condition}"/> --------------------------------------------------------------------------- Key: JBSEAM-1807 URL: http://jira.jboss.com/jira/browse/JBSEAM-1807 Project: JBoss Seam Issue Type: Feature Request Components: JSF Environment: all Reporter: Mikhail Grushinskiy Ability to conditionally add attributes to JSF components is needed Check this discussion http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116230 -- 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

18 years, 7 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1810) no-conversation-view-id malfunction or a need for improvement

by Przemyslaw Jaskierski (JIRA)

no-conversation-view-id malfunction or a need for improvement ------------------------------------------------------------- Key: JBSEAM-1810 URL: http://jira.jboss.com/jira/browse/JBSEAM-1810 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: Tomcat 6.0.13, latest Seam 2.0 snapshot Reporter: Przemyslaw Jaskierski Priority: Critical Fix For: 2.0.0.CR1 I have a bunch of views that are used by pageflow-defined conversation. Lets call them page1.xhtml, page2.xhtml, page3.xhtml. I want to prevent user from simply typing arbitrary url and accessing any view from those above. When a user types in a browser http://url.com/page2.xhtml he should be redirected to a configured no-conversation-view-id. That would be expected behaviour, but adding to the pages.xml file this section: <page view-id="/page2.xhtml" no-conversation-view-id="/invalidconversationerror.xhtml"/> Doesn't work, and user can enter with an undefined state into the middle of conversational pages chain. -- 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

18 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1435) Implement community-oriented user profile screen

by Christian Bauer (JIRA)

Implement community-oriented user profile screen ------------------------------------------------ Key: JBSEAM-1435 URL: http://jira.jboss.com/jira/browse/JBSEAM-1435 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Account management is done, however, user profile is something different (personal data, picture, etc.) -- 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

18 years, 7 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1753) Problems mixing a4j:support, @In and component binding

by Igor Fuchedzhi (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-1753?page=comments#action_12372727 ] Igor Fuchedzhi commented on JBSEAM-1753: ---------------------------------------- I have the same problems with @In annotation when I'm trying to inject any session (stateful or stateless) bean > Problems mixing a4j:support, @In and component binding > ------------------------------------------------------ > > Key: JBSEAM-1753 > URL: http://jira.jboss.com/jira/browse/JBSEAM-1753 > Project: JBoss Seam > Issue Type: Bug > Affects Versions: 2.0.0.BETA1 > Environment: ajax4jsf 1.1.1, JBoss Seam 1.2.1, Facelets 1.1.11, MyFaces 1.1.6 nightly from 20070614, Tomcat 5.5.23 > Reporter: Daniel Wiell > Assigned To: Alexander Smirnov > > Here is a simple example that shows how to reproduce this: > <?xml version='1.0' encoding='UTF-8'?> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:f="http://java.sun.com/jsf/core" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:a4j="https://ajax4jsf.dev.java.net/ajax"> > <head><title>Seam + ajax4jsf + binding</title></head> > <body> > <h:form> > Input: > <h:inputText binding="#{testController.input}" > value="#{testController.value}"> > <a4j:support event="onkeyup" reRender="repeater"/> > </h:inputText> > <br/> > Repeat: > <h:outputText id="repeater" value="#{testController.value}"/> > </h:form> > </body> > </html> > import org.jboss.seam.annotations.In; > import org.jboss.seam.annotations.Name; > import org.jboss.seam.core.FacesMessages; > import javax.faces.component.UIInput; > @Name("testController") > public class TestController { > @In > FacesMessages facesMessages; > private UIInput input; > private String value; > public UIInput getInput() { return input; } > public void setInput(UIInput input) { this.input = input; } > public String getValue() { return value; } > public void setValue(String value) { this.value = value; } > } > When entering something in the inputField, the following is thrown: > 2007-06-20 08:36:33,260 ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/geo].[faces] - Servlet.service() for servlet faces threw exception > org.jboss.seam.RequiredException: In attribute requires non-null value: testController.facesMessages > at org.jboss.seam.Component.getValueToInject(Component.java:1919) > at org.jboss.seam.Component.injectAttributes(Component.java:1368) > at org.jboss.seam.Component.inject(Component.java:1195) > at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) > at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27) > at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) > at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103) > at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151) > at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87) > at TestController_$$_javassist_0.setInput(TestController_$$_javassist_0.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.apache.myfaces.el.PropertyResolverImpl.setProperty(PropertyResolverImpl.java:409) > at org.apache.myfaces.el.PropertyResolverImpl.setValue(PropertyResolverImpl.java:176) > at org.apache.myfaces.custom.security.SecurityContextPropertyResolver.setValue(SecurityContextPropertyResolver.java:136) > at com.sun.facelets.el.LegacyELContext$LegacyELResolver.setValue(LegacyELContext.java:201) > at com.sun.el.parser.AstValue.setValue(AstValue.java:113) > at com.sun.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:246) > at com.sun.facelets.el.TagValueExpression.setValue(TagValueExpression.java:93) > at com.sun.facelets.el.LegacyValueBinding.setValue(LegacyValueBinding.java:68) > at org.apache.myfaces.shared_impl.util.RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid(RestoreStateUtils.java:86) > at org.apache.myfaces.shared_impl.util.RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid(RestoreStateUtils.java:57) > at org.apache.myfaces.shared_impl.util.RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid(RestoreStateUtils.java:94) > at org.apache.myfaces.shared_impl.util.RestoreStateUtils.recursivelyHandleComponentReferencesAndSetValid(RestoreStateUtils.java:57) > at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:96) > at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:95) > at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:53) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) > at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) > at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) > at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) > at java.lang.Thread.run(Thread.java:595) > Everything works fine if: the @In annotation is removed or the component binding is removed -- 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

18 years, 7 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 August 2007