[
https://issues.jboss.org/browse/SOLDER-49?page=com.atlassian.jira.plugin....
]
Dan Allen commented on SOLDER-49:
---------------------------------
I've documented what is required to get JBoss Logging to generate the proxies
dynamically in the absence of the concrete classes. We should still try to make that
easier on the developer, to be tracked in a separate issue.
Unsatisfied dependencies for type-safe logger
---------------------------------------------
Key: SOLDER-49
URL:
https://issues.jboss.org/browse/SOLDER-49
Project: Seam Solder
Issue Type: Bug
Components: Logging
Affects Versions: 3.0.0.Beta1
Reporter: Dan Allen
Assignee: Dan Allen
Priority: Blocker
Fix For: 3.0.0.Final
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