MBean interface and concrete class in different packages?
posted 6 years ago
When creating a standard MBean interface and its concrete class, can they not be declared in different packages? When I try to do this, I get the "xxx is not a compliant JMX standard mbean" etc NotCompliantMBeanException. When I put them in the same package, no errors. I didn't read anything about this restriction.
I want to be able to access my Mbean remotely, so I need to export the interface in a separate JAR file to the client, but not the concrete implementation. How can I do this if there is this packaging requirement?