January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2112) required parameters cause ValidatorException on postbacks

by Matt Drees (JIRA)

required parameters cause ValidatorException on postbacks --------------------------------------------------------- Key: JBSEAM-2112 URL: http://jira.jboss.com/jira/browse/JBSEAM-2112 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Environment: cvs from last week Reporter: Matt Drees Priority: Minor When you have a page with a required parameter, and you try to do a postback, Param.getStringValueFromRequest() throws a ValidatorException. -- 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-2459) Document to use hot deployment feature, SeamFilter needs to be activated

by Joshua Partogi (JIRA)

Document to use hot deployment feature, SeamFilter needs to be activated ------------------------------------------------------------------------ Key: JBSEAM-2459 URL: http://jira.jboss.com/jira/browse/JBSEAM-2459 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.1.CR1 Reporter: Joshua Partogi Priority: Minor On point 2.7 on the document we need to add that in order to activate hot deployment feature we also need to turn on SeamFilter on web.xml. This is to avoid ambiguation since on point 25.1.4 it is written that Seam doesn't need any servlet filters for basic operation. -- 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] Commented: (JBSEAM-2299) Seam Generate Entities creates edit field for @Version annotated fields

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=comments#action_12394082 ] Pete Muir commented on JBSEAM-2299: ----------------------------------- Looks good! > Seam Generate Entities creates edit field for @Version annotated fields > ----------------------------------------------------------------------- > > Key: JBSEAM-2299 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2299 > Project: JBoss Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Thorsten Kunz > Assigned To: Dan Allen > Priority: Minor > Fix For: 2.0.1.GA > > Attachments: JBSEAM-2299-v1.txt, JBSEAM-2299-v2.txt, JBSEAM-2299-v3.txt > > > When you have an entity with a @Version annotation present (which is the default if you create it with "Seam Entity") and then run "Seam Generate Entities" on the project and select "use existing entities" the resulting CRUD pages will allow the version field to be edited. So you won't be able to create entities because the set accessor for the version was declared private in the entity. This renders the CRUD pages useless. > I think this field should not be editable in the first place. > Cheers, Thorsten -- 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
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2464) add attributes to control title and legend on pie charts

by Dan Allen (JIRA)

add attributes to control title and legend on pie charts -------------------------------------------------------- Key: JBSEAM-2464 URL: http://jira.jboss.com/jira/browse/JBSEAM-2464 Project: JBoss Seam Issue Type: Feature Request Components: PDF Affects Versions: 2.0.1.CR1 Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.x Both line and bar charts allow the title and legend to be controlled. Pie charts support neither. The problem is that they do not extend from the same base class. The logic from the base class used by line and bar charts needs to ported to the pie chart component or the pie chart component needs to extend from UICategoryChartBase -- 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
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2299) Seam Generate Entities creates edit field for @Version annotated fields

by Dan Allen (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2299?page=all ] Dan Allen updated JBSEAM-2299: ------------------------------ Attachment: JBSEAM-2299-v3.txt Added filter to all places version property might be displayed. > Seam Generate Entities creates edit field for @Version annotated fields > ----------------------------------------------------------------------- > > Key: JBSEAM-2299 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2299 > Project: JBoss Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Thorsten Kunz > Assigned To: Dan Allen > Priority: Minor > Fix For: 2.0.1.GA > > Attachments: JBSEAM-2299-v1.txt, JBSEAM-2299-v2.txt, JBSEAM-2299-v3.txt > > > When you have an entity with a @Version annotation present (which is the default if you create it with "Seam Entity") and then run "Seam Generate Entities" on the project and select "use existing entities" the resulting CRUD pages will allow the version field to be edited. So you won't be able to create entities because the set accessor for the version was declared private in the entity. This renders the CRUD pages useless. > I think this field should not be editable in the first place. > Cheers, Thorsten -- 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
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2139) Exception redirect not propagating messages

by Matthew Lieder (JIRA)

Exception redirect not propagating messages ------------------------------------------- Key: JBSEAM-2139 URL: http://jira.jboss.com/jira/browse/JBSEAM-2139 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.CR2, 1.2.1.GA Reporter: Matthew Lieder Given the following in pages.xml: <exception> <end-conversation/> <redirect view-id="/error.jspx"> <message severity="error">#{org.jboss.seam.handledException.message}</message> </redirect> </exception> and the following in error.jspx: <h:messages /> redirection works (the error page displays), but the message is never shown. The problem's being seen when exceptions are being thrown from jPDL pageflow actions, and might be only reproducible under those situations (see the forum thread for more info). -- 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

5
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2014) Ajax event and navigation event clash, results in blank page

by Christian Bauer (JIRA)

Ajax event and navigation event clash, results in blank page ------------------------------------------------------------ Key: JBSEAM-2014 URL: http://jira.jboss.com/jira/browse/JBSEAM-2014 Project: JBoss Seam Issue Type: Bug Reporter: Christian Bauer Priority: Blocker Install the wiki and edit the start document. Now on the edit page, click into the Title field. Next, click on "Exit Editor". You will get a blank page (Firefox). Apparently there is a conflict between the onblur event that is triggered by leaving the Title text input field and the navigation event. This started to occur after one of the Richfaces updates in the last 10 days. -- 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-1986) entityQuery.getResultCount() fails if there is a join fetch in the ejbql

by Pete Muir (JIRA)

entityQuery.getResultCount() fails if there is a join fetch in the ejbql ------------------------------------------------------------------------ Key: JBSEAM-1986 URL: http://jira.jboss.com/jira/browse/JBSEAM-1986 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.CR1 Reporter: Pete Muir given "from Locality l join fetch l.region" as the ejbql, calling getResultCount() throws a Hibernate parsing exception javax.el.ELException: /index.xhtml: Error reading 'resultCount' on type org.jboss.seam.example.ui.LocalitiesQuery_$$_javassist_1 at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:150) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:613) Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list [FromElement{explicit,not a collection join,fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=Region,tableAlias=region1_,origin=Locality locality0_,colums={locality0_.region_id ,className=org.jboss.seam.example.ui.Region}}] [select count(*) from org.jboss.seam.example.ui.Locality l join fetch l.region where l.region.name = :el1] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:616) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:95) at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:79) at org.jboss.seam.framework.EntityQuery.createCountQuery(EntityQuery.java:167) at org.jboss.seam.framework.EntityQuery.initResultCount(EntityQuery.java:105) at org.jboss.seam.framework.EntityQuery.getResultCount(EntityQuery.java:97) 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.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.transaction.TransactionInterceptor$1.work(TransactionInterceptor.java:38) at org.jboss.seam.util.Work.workInTransaction(Work.java:40) at org.jboss.seam.transaction.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:32) 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.example.ui.LocalitiesQuery_$$_javassist_1.getResultCount(LocalitiesQuery_$$_javassist_1.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 javax.el.BeanELResolver.getValue(BeanELResolver.java:62) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64) at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java:53) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) at com.sun.facelets.el.ELText$ELTextVariable.writeText(ELText.java:184) at com.sun.facelets.el.ELText$ELTextComposite.writeText(ELText.java:108) at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:45) ... 41 more Caused by: org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list [FromElement{explicit,not a collection join,fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=Region,tableAlias=region1_,origin=Locality locality0_,colums={locality0_.region_id ,className=org.jboss.seam.example.ui.Region}}] [select count(*) from org.jboss.seam.example.ui.Locality l join fetch l.region where l.region.name = :el1] at org.hibernate.hql.ast.tree.SelectClause.initializeExplicitSelectClause(SelectClause.java:195) at org.hibernate.hql.ast.HqlSqlWalker.useSelectClause(HqlSqlWalker.java:705) at org.hibernate.hql.ast.HqlSqlWalker.processQuery(HqlSqlWalker.java:529) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:645) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:92) ... 77 more -- 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-2345) pages-2.0.xsd handling of <Navigation> doesn't allow standard rules and a null-accepting implicit rule

by Matt Drees (JIRA)

pages-2.0.xsd handling of <Navigation> doesn't allow standard rules and a null-accepting implicit rule ------------------------------------------------------------------------------------------------------ Key: JBSEAM-2345 URL: http://jira.jboss.com/jira/browse/JBSEAM-2345 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Matt Drees Priority: Minor pages-2.0.xsd doesn't allow something like this: <page view-id="/admin/manage/registrants/confirmDeleteRegistrant.xhtml"> <navigation from-action="#{registrantController.deleteSelectedRegistrant}"> <rule if="#{not empty registration.existingRegistrants}"> <redirect view-id="/admin/manage/registrants/showRegistration.xhtml"/> </rule> <redirect view-id="/admin/registrantSearching.xhtml"/> </navigation> </page> The XSD file doesn't allow a set of <rule>s *and* an implicit rule, even though Pages.java handles it correctly. -- 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

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2425) seam-gen / RF 3.1.3 simpleTogglePanel float clearing

by Andrew Atkinson (JIRA)

seam-gen / RF 3.1.3 simpleTogglePanel float clearing ---------------------------------------------------- Key: JBSEAM-2425 URL: http://jira.jboss.com/jira/browse/JBSEAM-2425 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.1.CR1 Reporter: Andrew Atkinson Fix For: 2.0.1.GA Apparently RF 3.1.3 moved from tables to css for the simpleTogglePanel layout and now the seam-gen generated display forms have some float clearing issue. To reproduce in a seam-gen generated project: <rich:simpleTogglePanel label="Lorem ipsum" switchType="client"> <s:decorate template="layout/display.xhtml"> <ui:define name="label">Lorem ipsum</ui:define> <h:inputText id="lorem1" value=""/> </s:decorate> </rich:simpleTogglePanel> As a workaround I added to theme.css: .rich-stglpanel-body { overflow: auto; } Not sure if this also applies to other RF components like panel. -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2008