BTW: Are you going to make jboss plugin compatible with jboss 3.2x


series?

What is not compatible? I seem to remember I have used it with JBoss
3.2.1.





maven.jboss.jmx.url.deploy=http://${maven.jboss.hostname}:${maven.jboss.
po


rt
}/jmx-
console/HtmlAdaptor?action=invokeOp&name=jboss.system:service%3DMainDe
ployer&methodIndex=19&arg0=



maven.jboss.jmx.url.undeploy=http://${maven.jboss.hostname}:${maven.jbos
s.


po
rt}/jmx-
console/HtmlAdaptor?action=invokeOp&name=jboss.system:service%3DMain
Deployer&methodIndex=2&arg0=


Perhaps there should be a maven.jboss.version property and a j:if tag would check that in order to invoke the right JMX thing. I seem to recall that the url was something different before we upgraded to 3.0.x...


<j:if test="${maven.jboss.version == '3.0.x'}">
 the stuff we have now...
</j:if>
<j:if test="${maven.jboss.version == '3.2.x'}">
 whatever is appropriate for 3.2.x...
</j:if>








ok, I haven't used those JMX deployments yet. The rest works with JBoss 3.2.x (the static deployment part).

Would you have a patch for the JMX stuff :-) ?

Thanks
-Vincent



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to