I'm trying to extend the management interface of my jbossmq queues, e.g. to add a web-based queue browser to the jmx console.

I think the easiest way would be to extend the jboss QueueManager class to add a browse() method, and expose that on the MBean. However, jboss uses package access for things like this.destination, so i can't access anything. If i change the access to protected, everything works fine.

Is this intentional? Making attributes like this protected would allow more white-box reuse and extension of the system.

The alternative seems to be to treat my mbean like any other component, and have it do JNDI lookups, create a queue browser, etc. Does anyone have a suggestion that is between these two solutions?