July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1635) Migrating to Drools 4.0.0 MR3

by Ning Zhao (JIRA)

Migrating to Drools 4.0.0 MR3 ----------------------------- Key: JBSEAM-1635 URL: http://jira.jboss.com/jira/browse/JBSEAM-1635 Project: JBoss Seam Issue Type: Feature Request Components: Drools Affects Versions: 2.0.0.BETA1 Environment: OS: all. JBoss AS 4.2.0 GA. Seam CVS 2007-07-10, Drools SVN 2007-07-10 Reporter: Ning Zhao Fix For: 2.0.0.CR1 Drools API has been changed since 4.0.0M3. Please see: http://wiki.jboss.org/wiki/Wiki.jsp?page=4.0.0.MR3ReleaseNotes Corresponding changes in the Seam codebase and Seam reference should be made if Drools 4.0 GA is to be used in the future Seam. -- 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, 5 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1663) deploying multiple examples on Tomcat fails from colliding Ejbs (TimerServiceDispatcher)

by Matt Drees (JIRA)

deploying multiple examples on Tomcat fails from colliding Ejbs (TimerServiceDispatcher) ---------------------------------------------------------------------------------------- Key: JBSEAM-1663 URL: http://jira.jboss.com/jira/browse/JBSEAM-1663 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: tomcat 6.0.13, embedded-jboss-beta2, seam-20070714.0506 Reporter: Matt Drees Priority: Minor When I deploy jboss-seam-booking and jboss-seam-dvd, the second app to be deployed fails with the following exception: org.jboss.deployers.spi.DeploymentException: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 is already registered at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:167) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:170) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:592) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:476) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:406) at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:128) at org.jboss.embedded.tomcat.WebinfScanner.lifecycleEvent(WebinfScanner.java:88) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4236) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) 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.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3 is already registered at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:80) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:465) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:410) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:392) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:358) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:313) at org.jboss.ejb3.deployers.EJBRegistrationDeployer.deploy(EJBRegistrationDeployer.java:157) ... 31 more I tried adding jboss-app.xml to the jar for each project, from seeing from the forum something about scoped classloading, but that didn't help any. -- 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, 5 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1163) <s:decorate> should nest children with <div> not <span>

by Darryl Smith (JIRA)

<s:decorate> should nest children with <div> not <span> ------------------------------------------------------- Key: JBSEAM-1163 URL: http://jira.jboss.com/jira/browse/JBSEAM-1163 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Reporter: Darryl Smith <s:decorate> nest its children within a span element. Using seam-gen produces <span> <-- from <s:decorate> <div class="prop"> ...... </div > </span> This is invalid HTML -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1685) ETag support

by Gavin King (JIRA)

ETag support ------------ Key: JBSEAM-1685 URL: http://jira.jboss.com/jira/browse/JBSEAM-1685 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Gavin King Would be nice to be able to have some API call like: ETag.instance().setTokenAndSendNotModified(...) which would set the ETag header, and send a not modified response if possible. -- 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, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1682) query restriction example: in ejbql the use of + operator appears to be wrong

by Wolfgang Schwendt (JIRA)

query restriction example: in ejbql the use of + operator appears to be wrong ----------------------------------------------------------------------------- Key: JBSEAM-1682 URL: http://jira.jboss.com/jira/browse/JBSEAM-1682 Project: JBoss Seam Issue Type: Bug Components: Documentation Environment: Seam2.0.0.B1 MySQL5.0.27 Reporter: Wolfgang Schwendt Priority: Trivial Fix For: 2.0.0.BETA1 The Seam reference manual, chapter "The Seam Application Framework", section "Query Objects", contains an example how one can specify optional restrictions for a query. More precisely, an XML definition of an EntityQuery component named "people" is shown. Two restrictions are defined, and it appears that the use of the + operator in these restrictions is wrong. In these restriction definitions the use of the + operator is intended for string concatenation, but according to JSR 220/EJB Persistence specification V.3.0 Final Release, the + operator is only listed in the category "arithmetic operators". At least when tested with Seam2.0.0B1 and MySQL, these restrictions (with the + operator) don't work as expected. Solution: replace the + operator by the concat() function as follows: <framework:entity-query name="people" ejbql="select p from Person p" order="lastName" max-results="20"> <framework:restrictions> <value>lower(firstName) like lower(concat ( #{examplePerson.firstName} , '%' ))</value> <value>lower(lastName) like lower(concat( #{examplePerson.lastName} + '%' ))</value> </framework:restrictions> </framework:entity-query> -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1674) HibernateSessionFactory creates a Factory on every DB operation

by Ralph Schaer (JIRA)

HibernateSessionFactory creates a Factory on every DB operation --------------------------------------------------------------- Key: JBSEAM-1674 URL: http://jira.jboss.com/jira/browse/JBSEAM-1674 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.0.BETA1 Environment: JavaBeans, Hibernate, Tomcat 6.0.13, Java 6, Windows XP Reporter: Ralph Schaer Priority: Blocker Reproduce with the Hibernate2 Example Deploying to tomcat works. The browser shows the login form. But everytime a new request is started for example with "Register New User" or "Register" in the New User form, the seam application creates a new HibernateSessionFactory and the SchemaExport tool is running. It drops and creates the tables in the database every time. So it's for example not possible to register a new user. The problem could be that org.jboss.seam.persistence.HibernateSessionFactory has a @Unwrap and a @Create method and both doing the same thing, call "return createSessionFactory();". If I understand the @Unwrap correctly the method will be called everytime the bean is referenced. This results in a new SessionFactory every time. I think the @Unwrap method schould only return the sessionFactory. -- 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, 5 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1652) Directory "view/exp" is missing for sample "hibernate2" in seam 2.0 beta

by Denis Forveille (JIRA)

Directory "view/exp" is missing for sample "hibernate2" in seam 2.0 beta ------------------------------------------------------------------------ Key: JBSEAM-1652 URL: http://jira.jboss.com/jira/browse/JBSEAM-1652 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.0.BETA1 Reporter: Denis Forveille Priority: Minor Directory "view/exp" is missing for sample "hibernate2" in seam 2.0 beta -- 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, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1600) Lowercase first letter of context variable for @Name

by Dan Allen (JIRA)

Lowercase first letter of context variable for @Name ---------------------------------------------------- Key: JBSEAM-1600 URL: http://jira.jboss.com/jira/browse/JBSEAM-1600 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor 99.99999999% of the time, when you want to create a Seam component, the convention is to use the simple name of the class with the first letter in lowercase. Open any Seam component in the examples directory and you will observe this conversion. Would it be reasonable to use the clazz.getSimpleName() and lowercase the first letter by default when creating the context variable? I would even settle for a configuration setting in core:manager that would enable this even if it were not used as the default. The change shouldn't cause compatibility issues since an explicit value is required as is. We are going around saying, "Look! Configuration by exception, see!" @Name("hotel") public class Hotel { ... } Um, hello. No. That is not configuration by exception. Let's make it that way! -- 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, 5 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1490) jboss-el for jBPM

by Gavin King (JIRA)

jboss-el for jBPM ----------------- Key: JBSEAM-1490 URL: http://jira.jboss.com/jira/browse/JBSEAM-1490 Project: JBoss Seam Issue Type: Feature Request Components: BPM Reporter: Gavin King Fix For: 1.3.1.GA jBPM does not currently support a pluggable EL engine, so we can't plug in jboss-el. -- 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, 5 months

1
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1677) SeamResourceBundle bundleCache always empty

by Darryl Smith (JIRA)

SeamResourceBundle bundleCache always empty ------------------------------------------- Key: JBSEAM-1677 URL: http://jira.jboss.com/jira/browse/JBSEAM-1677 Project: JBoss Seam Issue Type: Bug Reporter: Darryl Smith SeamResourceBundle.java:44 Locale instance = org.jboss.seam.core.Locale.instance(); if ( bundleCache.containsKey(instance) ) { bundleCache.put( instance, loadBundlesForCurrentLocale() ); } should be Locale instance = org.jboss.seam.core.Locale.instance(); if ( !bundleCache.containsKey(instance) ) { bundleCache.put( instance, loadBundlesForCurrentLocale() ); } -- 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, 5 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007