This has the same problem as the precedence.
When do you check that the class is available?
Under hotdeployment, the class could be added later and even removed and
redeployed.
When classloading dependencies are implemented (needs integration
between the classloader and the kernel - see other discussions)
a better feature might be to say:
| <bean ... class="org.drools.Shit" optional="true"/>
|
So if the class doesn't exist we don't report it as a missing dependency.
We just don't start the bean until somebody deploys the class.
This would also extend to other dependencies, not just classes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008927#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...