September 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMINTL-13) Support Java 6 ResourceBundle.Control

by Nicklas Karlsson (JIRA)

Support Java 6 ResourceBundle.Control ------------------------------------- Key: SEAMINTL-13 URL: https://jira.jboss.org/browse/SEAMINTL-13 Project: Seam i18n Issue Type: Feature Request Components: Messages Affects Versions: 3.0.0.Alpha1 Reporter: Nicklas Karlsson It would be nice to support ResourceBundle.Control so you could easily implement e.g. DB backed RB:s, timeouts etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] Created: (SEAMCRON-37) IllegalArgumentException: timeout value is negative

by Christian Kaltepoth (JIRA)

IllegalArgumentException: timeout value is negative --------------------------------------------------- Key: SEAMCRON-37 URL: https://issues.jboss.org/browse/SEAMCRON-37 Project: Seam Cron Issue Type: Task Affects Versions: 3.0.0.Alpha1 Environment: Tomcat 7.0.16, JDK6, Weld 1.1.0 Reporter: Christian Kaltepoth Assignee: Peter Royle I'm using Seam Cron to implement some background processing stuff in my application. Unfortunately after a few days the Quartz scheduler dies with this exception: {code} 2011-08-05 22:54:56,157 ERROR [QuartzSchedulerThread] Runtime error occured in main trigger firing loop. java.lang.IllegalArgumentException: timeout value is negative at java.lang.Object.wait(Native Method) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:296) {code} I did some research and found out that this is a known bug of Quartz 1.6.1. For details see the upstream issue: http://jira.opensymphony.com/browse/QUARTZ-707 This bug has been fixed in Quartz 1.6.2. So I think it would make sense to update the Quartz dependency of Seam Cron to the most recent Quartz version which is 1.6.5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4528) static pages don't work at all with database down and XA datasource used

by deanhiller (JIRA)

static pages don't work at all with database down and XA datasource used ------------------------------------------------------------------------ Key: JBSEAM-4528 URL: https://jira.jboss.org/jira/browse/JBSEAM-4528 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Environment: postgres or oracle with postgres or oracle XADatasource. postgres jdbc driver is fine while oracle driver is not Reporter: deanhiller Priority: Critical If this is a hibernate bug, please report hibernate issue and ticket here as other seam users will run into this problem and it looks like a seam framework problem(or at least could be solved in seam but it may be possible to solve in hibernate too and could be solved in each and every driver datasource as well). Steps to reproduce 1. start up the jboss 5.1.0 with latest seam 2. pull your internet connection so the db is gone 3. have all your customers go to a static page like /web/error.xhtml RESULT: jboss goes to it's knees as users in IE end up in infinite redirects to your server causing more and more load on the server. The drivers talk to the database when they should not be. I have a work around proxy driver for oracle's jdbc driver. I do not however have a fix for oracle's datasource or postgres datasource. I imagine someone could write a proxy datasource that would solve this problem for all people, hibernate, seam and all xa drivers. I will attach logs of postgres xa driver and oracle one but basically they are trying to open a connection to database when ANY http request comes in until waiting to see if we actually do any select statements or updates or inserts. For some reason, the postgres driver and oracle driver where fine here...they did not make db requests when an http request came in. The oracle driver however did make a request to the db when commit is called even if no sql was done against the db where postgres driver ignored the commit since no sql was done. I will try to attach files or more comments here. PLEASE if you report a tic in hibernate put it in here for others to find when they hit this issue. keyphrases: seam doesn't work when database goes down seam infinite redirect on db outage database failure causes seam to not work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
11
0 / 0

[JBoss JIRA] Created: (SEAMCRON-9) Should we expose exceptions during @Asynchronous via Future?

by Peter Royle (JIRA)

Should we expose exceptions during @Asynchronous via Future? ------------------------------------------------------------ Key: SEAMCRON-9 URL: https://issues.jboss.org/browse/SEAMCRON-9 Project: Seam Cron Issue Type: Enhancement Reporter: Peter Royle Assignee: Peter Royle Priority: Minor When an @Asynchronous method returns a Future, in EJB it allows you to access exceptions thrown by the @Asynchronous method via the returned Future object (EJB 3.1, 3.4.8). If possible we should mimic this behaviour. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-25) Add test cases for Glassfish 3.1

by John Ament (JIRA)

Add test cases for Glassfish 3.1 -------------------------------- Key: SEAMJMS-25 URL: https://issues.jboss.org/browse/SEAMJMS-25 Project: Seam JMS Issue Type: Enhancement Components: Injection Reporter: John Ament Assignee: John Ament Fix For: 3.0.0.Beta2 Need to add some test cases for glassfish v3.1, based on weld 1.1.1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
7
0 / 0

[JBoss JIRA] Created: (SEAMJMS-49) Fix JMS Status Watcher example.

by John Ament (JIRA)

Fix JMS Status Watcher example. ------------------------------- Key: SEAMJMS-49 URL: https://issues.jboss.org/browse/SEAMJMS-49 Project: Seam JMS Issue Type: Task Components: Event Bridging Affects Versions: 3.0.0.CR1 Reporter: Marek Schmidt Assignee: John Ament Fix For: 3.0.0.CR2 4. There are some old unused files in the jms-statuswatcher example that can probably be safely deleted: examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/qualifiers/StatusBridge.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/qualifiers/StatusTopic.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/RoutingConfig.java (unless wanted to be kept for illustrative purposes as an alternative approach to CdiJmsMapping) the following files have some unused imports: examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/ReceivingClient.java examples/jms-statuswatcher/src/main/java/org/jboss/seam/jms/example/statuswatcher/session/ReceivingClientListener.java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
5
0 / 0

[JBoss JIRA] Created: (SEAMCONFIG-50) Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) for

by Geoffrey De Smet (JIRA)

Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) for ----------------------------------------------------------------------- Key: SEAMCONFIG-50 URL: https://issues.jboss.org/browse/SEAMCONFIG-50 Project: Seam Config Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Geoffrey De Smet Assignee: Stuart Douglas Priority: Critical at least when running from the IntelliJ tomcat 6 plugin. Occurs for both exploded war and not exploded war. Strangely enough, it doesn't ignore it for the root xml schema validation. The problem is probably in ClasspathResourceLoader.getResources(String name): when name = "WEB-INF/beans.xml", it returnts an empty Set, while it should contain something like: /.../guvnor/guvnor-webapp/target/guvnor-webapp-5.3.0-SNAPSHOT/WEB-INF/beans.xml Thread.currentThread().getContextClassLoader() returns an instance of org.apache.catalina.loader.WebappClassLoader When asking Thread.currentThread().getContextClassLoader().getResourceAsStream("WEB-INF/beans.xml") or Thread.currentThread().getContextClassLoader().getResourceAsStream("/WEB-INF/beans.xml") it returns null (so the catalina WebappClassLoader returns null for that). yet asking a resource, such as Thread.currentThread().getContextClassLoader().getResourceAsStream("/drools-asseteditors.xml") does not return null, but the correct resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

13
33
0 / 0

[JBoss JIRA] Created: (SEAMFACES-44) View scope problems

by Aleksandar Pejovic (JIRA)

View scope problems ------------------- Key: SEAMFACES-44 URL: https://jira.jboss.org/browse/SEAMFACES-44 Project: Seam Faces Issue Type: Bug Affects Versions: 3.0.0.Alpha3 Environment: glassfish v3.0.1 Reporter: Aleksandar Pejovic 1.View scope should behave like normal scope, but client proxies aren't being used. 2.View scoped beans should be passivation capable, but the container isn't enforcing that. 3.@ViewScoped annotation cannot be used on producer methods/fields. More detailed description is available on a forum: http://seamframework.org/Community/SeamfacesViewScopeProblems -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

9
15
0 / 0

[JBoss JIRA] Created: (SEAM-88) Solder Property couldn't get property value if the property type is primitive.

by Miyazawa Yasushi (JIRA)

Solder Property couldn't get property value if the property type is primitive. ------------------------------------------------------------------------------ Key: SEAM-88 URL: https://issues.jboss.org/browse/SEAM-88 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Miyazawa Yasushi Property couldn't get property value if the property type is primitive. Simplest Test =================================================================================================== package org.miyazyss; import org.jboss.seam.solder.properties.Property; import org.jboss.seam.solder.properties.query.NamedPropertyCriteria; import org.jboss.seam.solder.properties.query.PropertyQueries; import org.jboss.seam.solder.properties.query.PropertyQuery; import org.junit.Assert; import org.junit.Test; /** * */ public class SolderMethodTest { public static class Bean { public long longValue = 1; public Long longClassValue = 3L; public long getLongValueMethod(){ return(2); } } private Bean bean = new Bean(); @Test public void testPrimitiveField(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> prop = query.addCriteria(new NamedPropertyCriteria("longValue")).getFirstResult(); Assert.assertEquals(1, prop.getValue(this.bean)); } @Test public void testPrimitiveReturnTypeMethod(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> propValue = query.addCriteria(new NamedPropertyCriteria("longValueMethod")).getFirstResult(); Assert.assertEquals(2, propValue.getValue(this.bean)); } @Test public void testClassField(){ PropertyQuery<Bean> query = PropertyQueries.createQuery(Bean.class); Property<Bean> propValue = query.addCriteria(new NamedPropertyCriteria("longClassValue")).getFirstResult(); Assert.assertEquals(3L, propValue.getValue(this.bean)); } } Result ========================================================================================================= SolderMethodTest org.miyazyss.SolderMethodTest testPrimitiveField(org.miyazyss.SolderMethodTest) java.lang.ClassCastException at java.lang.Class.cast(Unknown Source) at org.jboss.seam.solder.reflection.Reflections.getFieldValue(Reflections.java:682) at org.jboss.seam.solder.properties.FieldPropertyImpl.getValue(FieldPropertyImpl.java:75) at org.miyazyss.SolderMethodTest.testPrimitiveField(SolderMethodTest.java:37) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) testPrimitiveReturnTypeMethod(org.miyazyss.SolderMethodTest) java.lang.ClassCastException at java.lang.Class.cast(Unknown Source) at org.jboss.seam.solder.properties.MethodPropertyImpl.getValue(MethodPropertyImpl.java:136) at org.miyazyss.SolderMethodTest.testPrimitiveReturnTypeMethod(SolderMethodTest.java:45) 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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

6
6
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-38) ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager

by Daniel Kvasnička (JIRA)

ServletContextAttributeProvider uses wrong servlet ctx. attribute name to lookup the bean manager ------------------------------------------------------------------------------------------------- Key: SEAMSERVLET-38 URL: https://issues.jboss.org/browse/SEAMSERVLET-38 Project: Seam Servlet Issue Type: Bug Components: Event Bridge, Producers Affects Versions: 3.0.0.Final Environment: JDK6, Tomcat 6, weld-servlet 1.1.1.Final, seam-solder 3.0.0.Final, seam-servlet 3.0.0.Final Reporter: Daniel Kvasnička Priority: Critical org.jboss.seam.servlet.beanManager.ServletContextAttributeProvider uses BeanManager.class.getName() to lookup the bean manager in servlet context, but the name of the attribute used in sub-servlet3.0 containers is now org.jboss.weld.environment.servlet.Listener.BEAN_MANAGER_ATTRIBUTE_NAME -- AFAIK (see https://issues.jboss.org/browse/RESTEASY-471). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
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 September 2011