February 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMINTL-25) AvailableLocales.locales always has zero elements when configuration follows the documentation

by Leiv Hellebo (JIRA)

AvailableLocales.locales always has zero elements when configuration follows the documentation ---------------------------------------------------------------------------------------------- Key: SEAMINTL-25 URL: https://issues.jboss.org/browse/SEAMINTL-25 Project: Seam International Issue Type: Bug Components: Locales Affects Versions: 3.0.0.Beta2 Environment: JBAS6.0.0.Final Reporter: Leiv Hellebo AvailableLocales has @Produces List<Locale> locales, but the list is always empty Stepping through the code in debug mode shows that no locales is added because the if-test of line 55 (!supportedLocaleKeys.isUnsatisfied()) is never true (and a side note: the log says "WELD-000604 interface org.jboss.seam.international.locale.SupportedLocaleKeys is not declared @Target(METHOD, FIELD, PARAMETER, TYPE). Weld will use this annotation, however this may make the application unportable." otherwise nothing in the logs) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
7
0 / 0

[JBoss JIRA] Created: (SEAMINTL-5) Abillity to initialise locale and timezone for Application through Java, in addition to existing XML Config

by Ken Finnigan (JIRA)

Abillity to initialise locale and timezone for Application through Java, in addition to existing XML Config ----------------------------------------------------------------------------------------------------------- Key: SEAMINTL-5 URL: https://jira.jboss.org/browse/SEAMINTL-5 Project: Seam i18n Issue Type: Feature Request Components: Locales, Time zones Affects Versions: 3.0.0.Alpha1 Reporter: Ken Finnigan Fix For: 3.0.0.Alpha2 Add initialisation of Application Locale and TimeZone through Events. -- 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

15 years

2
4
0 / 0

[JBoss JIRA] Created: (SEAMINTL-1) TimeZone handling based on Seam 2

by Ken Finnigan (JIRA)

TimeZone handling based on Seam 2 --------------------------------- Key: SEAMINTL-1 URL: https://jira.jboss.org/jira/browse/SEAMINTL-1 Project: Seam i18n Issue Type: Task Reporter: Ken Finnigan Assignee: Pete Muir Develop similar functionality to that present in the existing Seam 2 source for handling timezones -- 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

15 years

3
8
0 / 0

[JBoss JIRA] Created: (SEAMINTL-2) Basic Locale Handling

by Ken Finnigan (JIRA)

Basic Locale Handling --------------------- Key: SEAMINTL-2 URL: https://jira.jboss.org/jira/browse/SEAMINTL-2 Project: Seam i18n Issue Type: Feature Request Components: Locales Reporter: Ken Finnigan Fix For: 3.0.0.Alpha1 Incorporate basic Locale handling and configuration similar to that present in Seam 2 -- 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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-3) Basic StatusMessage Handling

by Ken Finnigan (JIRA)

Basic StatusMessage Handling ---------------------------- Key: SEAMINTL-3 URL: https://jira.jboss.org/jira/browse/SEAMINTL-3 Project: Seam i18n Issue Type: Feature Request Components: Messages Reporter: Ken Finnigan Fix For: 3.0.0.Alpha1 Initial Status Message component that is basically a mirror of that within Seam 2. Create an initial stake in the ground for this to look to improve in time -- 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

15 years

2
2
0 / 0

[JBoss JIRA] Created: (SOLDER-62) Process logger annotations a build time

by Dan Allen (JIRA)

Process logger annotations a build time --------------------------------------- Key: SOLDER-62 URL: https://issues.jboss.org/browse/SOLDER-62 Project: Seam Solder Issue Type: Task Components: Logging Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 3.0.0.Beta2 Use the org.jboss.logging:jboss-logging-tools project to process the logger annotations at build time. We should not be relying on the jboss.i18n.generate-proxies system property inside a Seam module. If we remove the system property assignment, we need to document how developers can still enable that feature in their applications. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
8
0 / 0

[JBoss JIRA] Created: (SOLDER-45) Support @Veto at package level

by Dan Allen (JIRA)

Support @Veto at package level ------------------------------ Key: SOLDER-45 URL: https://jira.jboss.org/browse/SOLDER-45 Project: Seam Solder Issue Type: Feature Request Components: Core Reporter: Dan Allen Fix For: 1.0.0.Beta2 It would be useful to be able to veto an entire package of beans. The most typical use case is when you want to veto the JPA entities, which typically reside in the same package. It may be reasonable to add a recursive flag to veto all nested packages as well. Veto single package @org.jboss.seam.solder.Veto package com.acme.model; Veto package and descendants @org.jboss.seam.solder.Veto(recurse = true) package com.acme.model; If the recurse feature slows things down to much, we can forgo implementing it. Obviously recurse would be meaningless when @Veto is applied to a type, perhaps even considered a deployment error if set to true in that case. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (SOLDER-65) LoggerProducers is not initialized

by Alexey Elkin (JIRA)

LoggerProducers is not initialized ---------------------------------- Key: SOLDER-65 URL: https://issues.jboss.org/browse/SOLDER-65 Project: Seam Solder Issue Type: Bug Affects Versions: 3.0.0.Beta1 Environment: JBossAS 6.0.0.final Reporter: Alexey Elkin Priority: Critical I want to use logger in my java web application. I'm using JBossAS 6.0.0.final, cdi (weld), jsf ... etc. Seam solder proposes to use an abstract logger is not tying to a concrete implementation (slf4j, log4j, etc) using jboss-logging api. In order to get this logger in your code will need to write @ Inject org.jboss.logging.Logger log seam-solder.jar has the producer for this logger. package org.jboss.seam.solder.log; ... class LoggerProducers { @ Produces org.jboss.logging.Logger produceLog (InjectionPoint injectionPoint) {} } When I deploying my application, I get an error 15:51:18,300 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///C:/Java/jboss-6.0.0.Final/server/default/deploy/kamis-web-client.5.0.0-SNAPSHOT.ear_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [Logger] with qualifiers [@Default] at injection point [[field] @Inject private ru.kamis.suite.webclient.web.breadcrumbs.BreadcrumbsManager.log] This is due to the seam-solder.jar has not META-INF/beans.xml file, and it is necessary for cdi container. If to add beans.xml file in seam-solder.jar manually, then the application works WELL. How to do without hacks? To build my application I use maven, so my solution is not comfortable and NOT fine. PS: Former weld-extensions project contained META-INF/beans.xml file in jar. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (SOLDER-49) Unsatisfied dependencies for type-safe logger

by Dan Allen (JIRA)

Unsatisfied dependencies for type-safe logger --------------------------------------------- Key: SOLDER-49 URL: https://jira.jboss.org/browse/SOLDER-49 Project: Seam Solder Issue Type: Bug Components: Core Reporter: Dan Allen JBoss Logging caches the value of the system property jboss.i18n.generate-proxies, which determines whether it will generate the proxies that the type-safe loggers in Solder rely on. Although this property is set in a static block in the LoggerExtension, it may not be soon enough depending on the order that extension are loaded. In some cases, JBoss Logging caches a value of null, then all type-safe logging injection points break (and we get major complaints in the forums). You can fix this temporarily by starting the application server with the following system property: -Djboss.i18n.generate-proxies=true The real issue is in JBoss Logging. It shouldn't be caching this system property so aggressively. But the use of a system property in general is way too fragile. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
8
0 / 0

[JBoss JIRA] Created: (SOLDER-76) Incorporate use of amended Logging Tools Annotation Processor with Solder/Seam specific extension

by Ken Finnigan (JIRA)

Incorporate use of amended Logging Tools Annotation Processor with Solder/Seam specific extension ------------------------------------------------------------------------------------------------- Key: SOLDER-76 URL: https://issues.jboss.org/browse/SOLDER-76 Project: Seam Solder Issue Type: Enhancement Components: Logging Affects Versions: 3.0.0.Beta2 Reporter: Ken Finnigan Either as a separate Solder Tooling module, or directly within Solder itself, include the Solder/Seam specific implementation of the annotation processing tool that utilizes the core component to generate classes at build time for Logging and Messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2011