Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: 3.0.0.Beta1
-
Fix Version/s: 3.0.0.Final
-
Component/s: Logging
-
Labels:None
-
Estimated Difficulty:Low
Description
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.
Gliffy Diagrams
Issue Links
- is blocked by
-
JBLOGGING-52
Use of system property for proxy generation setting is too inflexible
-
- Closed
-
-
SOLDER-76
Incorporate use of amended Logging Tools Annotation Processor with Solder/Seam specific extension
-
- Resolved
-
- is duplicated by
-
SOLDER-65
LoggerProducers is not initialized
-
- Resolved
-
Resolve immediate issue by using jboss-logging-tools to generate the concrete class for AnnotatedMessages.
We still have a wider issue of documenting how this requirement affects consumers of the API.