November 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMINTL-62) Inline Message Translations

by Ken Finnigan (JIRA)

Inline Message Translations --------------------------- Key: SEAMINTL-62 URL: https://issues.jboss.org/browse/SEAMINTL-62 Project: Seam International Issue Type: Enhancement Components: Locales, Messages Reporter: Ken Finnigan Assignee: Ken Finnigan @Messages({ @Message(lang = "en", value = "hi"), @Message(lang = "fr", value = "bonjour")}) or @LocalizedMessages({ @Message(lang = "en", value = "hi"), @Message(lang = "fr", value = "bonjour")}) Allows definition of default language i.e. @Message(value = "hi", locale = "en") -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-63) i18n Catch Module messages

by Ken Finnigan (JIRA)

i18n Catch Module messages -------------------------- Key: SEAMINTL-63 URL: https://issues.jboss.org/browse/SEAMINTL-63 Project: Seam International Issue Type: Task Components: Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Priority: Minor Provide an example/documentation of how to internationalize messages that are created within the Seam Catch module -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-60) Double Byte support for Type Safe Messages

by Ken Finnigan (JIRA)

Double Byte support for Type Safe Messages ------------------------------------------ Key: SEAMINTL-60 URL: https://issues.jboss.org/browse/SEAMINTL-60 Project: Seam International Issue Type: Enhancement Components: Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Verify that a type safe message can use double byte chars in it's definition, and that it is retrieved correctly. XML version of properties files is supported as they can be UTF-8 Make XML version the default. See Wicket for ideas (https://issues.apache.org/jira/browse/WICKET-2035) Can do .utf8.properties in Java 6 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] (SEAMINTL-73) Create Tooling module to support i18n specific features

by Ken Finnigan (Created) (JIRA)

Create Tooling module to support i18n specific features ------------------------------------------------------- Key: SEAMINTL-73 URL: https://issues.jboss.org/browse/SEAMINTL-73 Project: Seam International Issue Type: Feature Request Components: Locales, Messages Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: 3.2.0.Alpha1 Add a tooling module to i18n build, similar to Solder, but it needs to take it a step further and have it's own annotation processor rather than using the one from JBoss Logging Processor, so that we can provide additional features within the generated classes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[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

12 years, 6 months

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

12 years, 6 months

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

12 years, 6 months

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

12 years, 6 months

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

12 years, 6 months

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

12 years, 6 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2011