This can be achieved by running with a security manager and assigning the core service layer jars the approriate permission while not allowing write access from the jmx-console.war or jmx-invoker-service.xml. You can partition out the untrusted access paths into a seperate deploy directory that is not assigned any write permissions.
More generically you would have configure the mbean as an xmbean with a security interceptor that imposed the can access semantics you are looking for. This would require a run-as security interceptor on the SARDeployer in order for it to be seen as a trusted component. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864425#3864425 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864425 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
