I already managed to get zabbix-java-gateway working with the Wildfly using some dirty hack. But today I had a more difficult case — client had both "old school" JMX servers available with rmi, and modern JMX available over http-remoting-jmx.
I had to write a custom solution for this client, but it can be useful for everyone who's got both old and new JMX servers. We established a convention: modern Wildfly servers use 10990 port, rmi servers use other ports. I've implemented the following customization (yes, sort of hack):
if (port == 10990) {
url = new JMXServiceURL("service:jmx:http-remoting-jmx://" + conn + ":" + port);
} else {
url = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + conn + ":" + port + "/jmxrmi");
}
This binary is available, and you can use it if you wish: http://baron.su/s/zabbix-java-gateway-2.4.4.jar. If you got wildfly or other JMX server which is working over http-remoting-jmx, you just need to make sure it's using 10990 port for JMX. You will also need to replace zabbix standard binary with mine. You'll also need to make sure that credentials are filled in every item in zabbix dashboard. Also zabbix-java-gateway should have jar files with the http-remoting-jmx protocol implementation.
If you didn't succeeded, please feel free to hire me (My skype is balkinrn and my jabber is ruslanbalkin@gmail.com), it's just one hour and everything will be done. Also I can build customized zabbix-java-gateway for your needs.