[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
[JBoss JIRA] Created: (SEAMFACES-94) Add @Named to producer for ExternalContext
by Dan Allen (JIRA)
Add @Named to producer for ExternalContext
------------------------------------------
Key: SEAMFACES-94
URL: https://issues.jboss.org/browse/SEAMFACES-94
Project: Seam Faces
Issue Type: Enhancement
Affects Versions: 3.0.0.CR1
Reporter: Dan Allen
Fix For: 3.0.0.Final
JSF exposes facesContext as an implicit EL variable that references the current FacesContext. However, no such implicit EL variable is available for ExternalContext. There is useful information in the ExternalContext that is often needed in the UI, particular during development. Thus, we should expose this implicit variable by adding @Named to the producer for ExternalContext.
@Named
@Produces
@RequestScoped
public ExternalContext getExternalContext(final FacesContext context) {
return context.getExternalContext();
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (SEAMPERSIST-34) drop persistence from the org.jboss.seam.persistence.transaction package
by Dan Allen (JIRA)
drop persistence from the org.jboss.seam.persistence.transaction package
------------------------------------------------------------------------
Key: SEAMPERSIST-34
URL: https://issues.jboss.org/browse/SEAMPERSIST-34
Project: Seam Persistence
Issue Type: Task
Affects Versions: 3.0.0.CR1
Reporter: Dan Allen
Fix For: 3.0.0.Final
The transaction APIs in Seam Persistence should be moved from:
org.jboss.seam.persistence.transaction
to:
org.jboss.seam.transaction.
Nesting the transaction package under the persistence package locks us into a tight coupling between orthogonal concerns. It also causes some misconception that the transaction features can only be used with persistence.
Although we've decided that the transaction APIs alone don't warrant their own module, we can still have two separate packages within this module.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years