You're comparing apples and oranges here. JMX is not a replacement for SNMP, WS-Management or any other management protocol. JMX provides the internal infrastructure needed by Java programs to expose their components for management.
There is an RMI-connector for JMX that lets one do JMX operations remotely, but there's also SNMP-connector that allows managing JMX resources (MBeans) using SNMP. And if WS-Management will become useful, I'm sure there will be a WS-Managemen connector for JMX.
So JMX is not going to take over the world, but will work with whatever standards the rest of the world uses.
Actually, Linus created more than just a kernel: he created a development process. We might take it for granted now, but the process didn't really exist in it's current form before Linux kernel.
Slashdot Mirror
You're comparing apples and oranges here. JMX is not a replacement for SNMP, WS-Management or any other management protocol. JMX provides the internal infrastructure needed by Java programs to expose their components for management.
There is an RMI-connector for JMX that lets one do JMX operations remotely, but there's also SNMP-connector that allows managing JMX resources (MBeans) using SNMP. And if WS-Management will become useful, I'm sure there will be a WS-Managemen connector for JMX.
So JMX is not going to take over the world, but will work with whatever standards the rest of the world uses.
Actually, Linus created more than just a kernel: he created a development process. We might take it for granted now, but the process didn't really exist in it's current form before Linux kernel.