DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12404>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12404 Protected Applications Summary: Protected Applications Product: Avalon Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Phoenix AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In some sitations it would be desirable for a .sar application to have access to certain services from the kernel. Each application may have access to such facilities as; * MBeanServer * Log/Config Manager for self * Log/Config Manager for all applications * Kernel objects like Deployer (to deploy other applications), Embeddor ( to shutdown server) etc. However in general we don't want one application to be able to interfere with another application. Nor do we want to expose the innerts of server to application (it limits evolution and requires significant classloader sharing). However, if we allowed such things as Application accessible kernel components then we open the door to implementation of many of the kernel components as regular applications. We could easily implement PR 8960 (a monitor that watches a directory and auto deploys) as a regular application. We could also implement a management console as a regular application. Regular applications are much easier to write as they have access to te full set of cornerstone (and other) components. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
