Peter Royle commented on WELDSE-24:
I like your suggestion to use Instance<Runnable>, and will likely end up taking that
on board as an additional barrier against users experiencing this exception. However I
first want to understand why you are experiencing this exception at all.
In my experience, since RunnableDecorator is a decorator, then unless it is enabled as a
decorator in beans.xml it shouldn't be a target for injection at all, unless you are
instantiating it some other way. I've just done a test which demonstrates this, which
I'll attach. Try running the project (most easily done in NetBeans since that's
where it was created, but also possible from the command line with some maven building and
manual classpath wizardry) with the decorator enabled versus commented out.
I don't suppose you have the decorator enabled in your beans.xml?
Are you causing RunnableDecorator to be instantiated any other way? Injecting it somewhere
Otherwise, what am I missing?
Thanks for your feedback.
RunnableDecorator incorrectly assumes >0 Runnable beans
Project: Weld support for Java SE
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: Java 6 + WeldSE
Reporter: Morten Christensen
The class org.jboss.weld.environment.se.threading.RunnableDecorator incorrectly assumes
that there will be at least one bean that implements Runnable.
If there are no beans that implements Runnable then an error like this will happen:
org.jboss.weld.DeploymentException: Injection point has unstatisfied dependencies.
Injection point: field org.jboss.weld.environment.se.threading.RunnableDecorator.runnable;
I guess the field "runnable" inside this class should be changed to use
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira