October 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-912) Add AJAX CLI

by Christian Bauer (JIRA)

Add AJAX CLI ------------ Key: JBSEAM-912 URL: http://jira.jboss.com/jira/browse/JBSEAM-912 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor A power-user CLI that I can bring up and type in commands in a simple language, with auto-completion and immediate help. Examples "view user christian blog" "edit An Area|This Document" "view This Directory" "create doc An Area|New Document" "create dir An Area|New Directory" "alter menu add This Document" "alter menu remove This Directory" "search doc "Search Terms"" 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

16 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1438) Integrate subetha

by Christian Bauer (JIRA)

Integrate subetha ----------------- Key: JBSEAM-1438 URL: http://jira.jboss.com/jira/browse/JBSEAM-1438 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Integrate subetha mailing list manager. Probably requires a new ML management interface based on a plugin but using the subetha domain model. -- 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, 10 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1889) Seam text headline level handling has implicit dependencies

by Christian Bauer (JIRA)

Seam text headline level handling has implicit dependencies ----------------------------------------------------------- Key: JBSEAM-1889 URL: http://jira.jboss.com/jira/browse/JBSEAM-1889 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Priority: Minor In Seam text you can not create a + Headline after you already have a ++ Headline. Also, if you create a +++ Headline it will be rendered as a ++ Headline, 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

16 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1881) seam-gen generate-entities not generating anything

by Marc Lustig (JIRA)

seam-gen generate-entities not generating anything -------------------------------------------------- Key: JBSEAM-1881 URL: http://jira.jboss.com/jira/browse/JBSEAM-1881 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.BETA1 Environment: win2000, MSSQL2000 Reporter: Marc Lustig seam generate-entities runs thru without any exception but is not generating anything. The JDBC-driver is loaded and hbm2java is being configured, but the actual code generation is not being triggered. (my console output is analogous to what pablodiablo posted in 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

16 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1786) entity-query : resultCount fails if query has "join fetch"

by Fernando Montaño (JIRA)

entity-query : resultCount fails if query has "join fetch" ----------------------------------------------------------- Key: JBSEAM-1786 URL: http://jira.jboss.com/jira/browse/JBSEAM-1786 Project: JBoss Seam Issue Type: Bug Components: Framework Reporter: Fernando Montaño The following query fails when EntityQuery tries to get the result count: <framework:entity-query name="products" ejbql="from Product p join fetch p.drug" order="id" /> The exception thrown: javax.faces.el.EvaluationException: /admin/products.xhtml @25,117 rendered="#{products.resultCount == 0}": Exception getting value of property resultCount of base of type : org.jboss.seam.framework.EntityQ uery_$$_javassist_29 at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:60) at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java:1075) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:241) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) at com.sun.facelets.tag.jsf.ComponentSupport.encodeRecursive(ComponentSupport.java:249) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:573) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:229) 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) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) 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.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:202 ) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202 ) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202 ) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base Protocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Unknown Source) Caused by: javax.faces.el.EvaluationException: Bean: org.jboss.seam.framework.EntityQuery_$$_javassi st_29, property: resultCount at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:442) at org.apache.myfaces.el.PropertyResolverImpl.getValue(PropertyResolverImpl.java:82) at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:141) at com.sun.el.parser.AstValue.getValue(AstValue.java:125) at com.sun.el.parser.AstEqual.getValue(AstEqual.java:41) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:195) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:56) ... 45 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.myfaces.el.PropertyResolverImpl.getProperty(PropertyResolverImpl.java:438) ... 52 more Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryException: query specified join fe tching, but the owner of the fetched association was not present in the select list [FromElement{exp licit,not a collection join,fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName =Drug,tableAlias=drug1_,origin=Product product0_,colums={product0_.DRUG_ID ,className=com.rmemoria.d rugman.entities.Drug}}] [select count(*) from com.rmemoria.drugman.entities.Product p join fetch p.d rug ] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl. java:634) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:95) at org.jboss.seam.persistence.EntityManagerProxy.createQuery(EntityManagerProxy.java:72) at org.jboss.seam.framework.EntityQuery.createCountQuery(EntityQuery.java:127) at org.jboss.seam.framework.EntityQuery.getResultCount(EntityQuery.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:57) at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:34) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.TransactionInterceptor$1.work(TransactionInterceptor.java:32) at org.jboss.seam.util.Work.workInTransaction(Work.java:37) at org.jboss.seam.interceptors.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:27) 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 org.jboss.seam.framework.EntityQuery_$$_javassist_29.getResultCount(EntityQuery_$$_javassist_29. java) ... 57 more Caused by: org.hibernate.QueryException: query specified join fetching, but the owner of the fetched assoc 11:46:22,640 ERROR [STDERR] iation was not present in the select list [FromElement{explicit,not a co llection join,fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=Drug,tableAli as=drug1_,origin=Product product0_,colums={product0_.DRUG_ID ,className=com.rmemoria.drugman.entitie s.Drug}}] [select count(*) from com.rmemoria.drugman.entities.Product p join fetch p.drug ] at org.hibernate.hql.ast.tree.SelectClause.initializeExplicitSelectClause(SelectClause.java:195) at org.hibernate.hql.ast.HqlSqlWalker.useSelectClause(HqlSqlWalker.java:712) at org.hibernate.hql.ast.HqlSqlWalker.processQuery(HqlSqlWalker.java:536) 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) ... 79 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1775) Schema is a little confusing...

by Tony Herstell (JIRA)

Schema is a little confusing... ------------------------------- Key: JBSEAM-1775 URL: http://jira.jboss.com/jira/browse/JBSEAM-1775 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Tony Herstell Priority: Minor Doco is confusing due to schema requiring different names for attributes in different places. <action expression <action execute --> Slightly confusingly, if you want to put an action in a < page> element in pages.xml, you use "execute", not "expression". -- 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, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1598) include "Clear" button for seam-gen search form

by Dan Allen (JIRA)

include "Clear" button for seam-gen search form ----------------------------------------------- Key: JBSEAM-1598 URL: http://jira.jboss.com/jira/browse/JBSEAM-1598 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor The search is a very nice feature to have on the list pages generated by seam-gen, but I have watched people (and struggled myself) with figuring out how to clear the current filter. It is very annoying to have to manually erase all the values entered in the form and then submit the form again once cleared. Far easier would be to have a Clear button on this form. The following button would do the trick. <h:commandButton id="clear" value="Clear" onclick="for (var i = 0, len = this.form.length; i < len; i++) { if (this.form[i].type == 'text') { this.form[i].value = ''; } }" action="/${listPageName}.xhtml"/> I will admit that the JavaScript is a little hacky, but it gets the point across. Feel free to refine. -- 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, 10 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1454) DataSource connectionURL property

by Markus Wolf (JIRA)

DataSource connectionURL property --------------------------------- Key: JBSEAM-1454 URL: http://jira.jboss.com/jira/browse/JBSEAM-1454 Project: JBoss Seam Issue Type: Bug Reporter: Markus Wolf Priority: Blocker The datasource connectionURL property does not allow whitespaces around it. It would be better to add a trim for this in the xml parser code. -- 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, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1310) page configuration parameter no-cache

by Leo Baschy (JIRA)

page configuration parameter no-cache ------------------------------------- Key: JBSEAM-1310 URL: http://jira.jboss.com/jira/browse/JBSEAM-1310 Project: JBoss Seam Issue Type: Patch Components: Core Affects Versions: 1.2.1.GA Environment: all Reporter: Leo Baschy Have implemented page configuration parameter no-cache. It effects HTTP headers to say no-cache. Waiting for JBSEAM-1009 to submit a patch because it changes some of the same files as JBSEAM-1009 so it would be a mixed patch unless we'd bother to make a separate copy of the project etc... So if 1009 is in we should follow up with this no-cache patch. For no-cache we've also used the same pattern of allowing more specific paths/directories to override less specific directories, if someone cares to set it that way. Better way. Means DTD must use <!ATTLIST page no-cache (true|false) #IMPLIED> and must NOT be <!ATTLIST page no-cache (true|false) "false"> and internally in Page it is coded to store as object Boolean to allow null if not set, it does NOT store primitive boolean. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1182) Meldware not working on 4.2

by Pete Muir (JIRA)

Meldware not working on 4.2 --------------------------- Key: JBSEAM-1182 URL: http://jira.jboss.com/jira/browse/JBSEAM-1182 Project: JBoss Seam Issue Type: Bug Components: Examples, Mail Reporter: Pete Muir Fix For: 1.3.0.BETA1 -- 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, 10 months

2
7
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