You could allways write a constructor taking the necessary arguments. In your jboss-service.xml you would then get code like
It doesn't answer your question, but might solve your problem, I guess.
JMX attributes differ from plain JavaBeans properties in the case of the first letter of the attribute name.
So, in JMX if you have a pair of methods
public String getRootPath()
public void setRootPath(String path)
these define a read/write attribute called 'RootPath', not 'rootPath', while in plain JavaBeans they would identify a property called 'rootPath' (note the case of the first letter).
That might be it, but shouldn't I see an error that "rootPath" is not a valid property?
submit a patch with the logic to display that, the logic in 3.0 is in the ServiceController and ServiceConfigurator.java (under org.jboss.system)
ServiceConfigurator already throws a
DeploymentException in RH when the attribute cannot be