An ear is the simplest solution.
You can use a in jboss.xml
to force loading of the dependent bean or jar
use http://localhost:8080/jmx-console for the full names
If you don't plan to hot-deploy, you can number the
see jboss-service.xml for the config changes
to enable the prefix scanner.
> An ear is the simplest solution.
> You can use a in jboss.xml
> to force loading of the dependent bean or jar
Does this go at the top level of the jboss.xml file, e.g.:
Or do you need to put it in the bean declaration:
I looked in the DTD for jboss.xml but didn't find anything about it.
> If you don't plan to hot-deploy, you can number the
> see jboss-service.xml for the config changes
> to enable the prefix scanner.
Also, why does hot deploy come into this? As I understand it, if you started up the server with 10-... and 20-... and then redeployed 20-..., everything would still be consistent. And if you redeployed 10-... then there would be a problem for beans in 20-... while it was redeploying, but after it would be ok.
Of course, I could be wrong :-)
It is per bean
You can use any jmx ObjectName and have multiple .
You can also specify dependencies against
If you redeploy
20-mesecond.jar is not redeployed so it may
hold references to old classes from 10-loadmefirst.jar
you will get ClassCastExceptions
The prefix stuff only works during the initial boot.
I've tried both:
And I still get the following error at startup:
Depends On Me: org.jboss.deployment.DeploymentException: Exception setting attribute javax.management.Attribute@49eb9f on mbean jboss:service=Scheduler; - nested throwable: (java.security.InvalidParameterException: Given class Whatever is not valid or not found)]
However everything is ok if I re-deploy my xxx-service.xml after.
Do I miss something?
Since we're on the subject of .. I've been trying to find out whether or not it's going to be documented in the dtd for JBoss.xml
Currently, it doesn't seem to be and I'm trying to get an XDoclet patch that supports generation of the attribute committed. The lack of dtd documentation is holding it up.