The methods on the MBeanRegistration interface are completely irrelevant to the interface exposed by an MBean.
Again, it's a matter of applying security constraints to the invocation of an attribute (i.e. who's calling me?) But because this is a bit complicated, I reckon the best solution for you is to provide an MBean CTOR that will allow you more or less to initialise the MBean with whatever settings at the begging, and either don't expose those settings at all as attributes, or expose them as read only attributes. You can pass CTOR arguments when you deploy your service, see docs/dtd/jboss-service_4_0.dtd View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867166#3867166 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867166 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
