April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2302) Query Parser adding Where clause conditions to Non Where clauses

by Terry (JIRA)

Query Parser adding Where clause conditions to Non Where clauses ---------------------------------------------------------------- Key: JBSEAM-2302 URL: http://jira.jboss.com/jira/browse/JBSEAM-2302 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Terry When using EntityQuery's getEjbql() and getRestrictions() override methods; and if ejbql in getEjbql() contains any clause after the WHERE clause - such as GROUP BY, the query parses appends restrictions to GROUP BY clause rather than to the WHERE clause. It seems, that EntityQuery expects WHERE to be last clause in ejbql. -- 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, 8 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2804) code samples in tables are over flowing their borders

by Jay Balunas (JIRA)

code samples in tables are over flowing their borders ----------------------------------------------------- Key: JBSEAM-2804 URL: http://jira.jboss.com/jira/browse/JBSEAM-2804 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR1 In the Reference guide chapter 16 and chapter 28 (may be others as well) there are code samples embedded within a table. They are overlapping the table boundaries. I thought it was a formatting problem - that type of thing happens a lot with css issues on webpages. -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2842) "ant deploypresentation" attempt to deploy to jbossweb-tomcat55.sar

by Jay Balunas (JIRA)

"ant deploypresentation" attempt to deploy to jbossweb-tomcat55.sar ------------------------------------------------------------------- Key: JBSEAM-2842 URL: http://jira.jboss.com/jira/browse/JBSEAM-2842 Project: JBoss Seam Issue Type: Bug Components: Build, Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.GA When you run ant deploypresentation it attempts to deploy to "jbossweb-tomcat55.sar" which does not exist in JBoss 4.2. It throws the exception below. 14:07:09,396 ERROR [MainDeployer] Could not initialise deployment: file:/jboss/apps/jboss-4.2.2.GA/server/default/deploy/jbossweb-tomcat55.sar/ org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jbossweb-tomcat55.sar at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:616) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:181) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2812) GroovyHotDeploymentStrategy not reloading Java classes

by Dan Allen (JIRA)

GroovyHotDeploymentStrategy not reloading Java classes ------------------------------------------------------ Key: JBSEAM-2812 URL: http://jira.jboss.com/jira/browse/JBSEAM-2812 Project: JBoss Seam Issue Type: Bug Components: Hot Deploy Affects Versions: 2.0.1.CR2 Reporter: Dan Allen Assigned To: Pete Muir Fix For: 2.0.2.CR1 The logic that checks if a class is from the hot deploy classloader in GroovyHotDeploymentStrategy does not properly detect Java classes. It needs to delegate to the superclass before looking for Groovy classes. You can verify this problem by examining the value expression #{init.hotDeployableComponents} in a JSF view. -- 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, 8 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2813) Change port used by remoting-service.xml in Embedded JBoss to prevent interfering with running JBoss AS

by Dan Allen (JIRA)

Change port used by remoting-service.xml in Embedded JBoss to prevent interfering with running JBoss AS ------------------------------------------------------------------------------------------------------- Key: JBSEAM-2813 URL: http://jira.jboss.com/jira/browse/JBSEAM-2813 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.1.CR2 Reporter: Dan Allen Assigned To: Pete Muir Priority: Minor Fix For: 2.0.1.CR2 There is only one configuration setting preventing the Embedded JBoss runtime used by SeamTest from working while a JBoss AS is running on the same machine (in its default configuration). The port specified in remoting-service.xml needs to be change to something other than 3873. -- 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, 8 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2839) Blog example does not document that the password is "tokyo".

by Jay Balunas (JIRA)

Blog example does not document that the password is "tokyo". ------------------------------------------------------------ Key: JBSEAM-2839 URL: http://jira.jboss.com/jira/browse/JBSEAM-2839 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR2 In order to login to the Blog example you need search the import.sql file and find that the password is "tokyo". It should be in the readme, and/or the view. -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2807) Add comment to jndiPattern in example's component.properties files

by Stephen Friedrich (JIRA)

Add comment to jndiPattern in example's component.properties files ------------------------------------------------------------------ Key: JBSEAM-2807 URL: http://jira.jboss.com/jira/browse/JBSEAM-2807 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Reporter: Stephen Friedrich The Seam reference says that patterns in components.xml like @jndiPattern@ can be replaced at runtime with corresponding values from components.properties if that file is on the class path. It is confusing, though that each example's components.xml contains {code}<core:init jndi-pattern="@jndiPattern@" debug="true"/>{code} and the components.properties contains {code}jndiPattern #{ejbName}/local{code} However when running on the default app server (JBoss) the components.xml gets changed at runtime to {code}<core:init jndi-pattern="jboss-seam-booking/#{ejbName}/local" debug="true"/>{code} Please add a comment to components.properties like "The pattern in components.xml is replaced by an application server specific value by ant. This value here is for running tests only:" -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2843) seam-examples.html and examples/readme.txt needs to updated/reviewed

by Jay Balunas (JIRA)

seam-examples.html and examples/readme.txt needs to updated/reviewed -------------------------------------------------------------------- Key: JBSEAM-2843 URL: http://jira.jboss.com/jira/browse/JBSEAM-2843 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.CR2 examples/readme.txt - - links updated for sfwk.org, - list of examples updated - Versions of JBoss changed to 4.2.2 examples/seam-examples.html - ant deploypresentation has been removed - the list of examples needs updating - Perhaps the page could go away if not used. -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2848) JPA example readme.txt for JBoss says that you need to deploy manually, but it is done.

by Jay Balunas (JIRA)

JPA example readme.txt for JBoss says that you need to deploy manually, but it is done. ---------------------------------------------------------------------------------------- Key: JBSEAM-2848 URL: http://jira.jboss.com/jira/browse/JBSEAM-2848 Project: JBoss Seam Issue Type: Task Components: Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Trivial Fix For: 2.0.2.CR2 Very minor update to readme.txt. The readme.txt says the JBoss example needs to be deployed manually, but it is done by the build. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2841) Seamdisc example's "ant undeploy" does not remove ear, or exploded dir

by Jay Balunas (JIRA)

Seamdisc example's "ant undeploy" does not remove ear, or exploded dir ---------------------------------------------------------------------- Key: JBSEAM-2841 URL: http://jira.jboss.com/jira/browse/JBSEAM-2841 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Optional This is just a consistency issue. Most of the other examples "ant undeploy" removes all of the artifacts from JBoss. This undeploy only removed the "-ds.xml" file - not the EAR or the exploded directory. -- 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, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2008