[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Scott Hasse commented on AS7-1389: ---------------------------------- With respect to point 6, for the most part I understand where you are coming from. JEE vendors are encouraged to differentiate themselves on features and extensions. I think many people believe the JEE specification is deficient with respect to the lack of a specified logging facility beyond java.util.logging and the ServletContext's log methods. This makes container logging a potentially good opportunity for vendors to differentiate themselves. So more power to you to provide a logging facility as far as I am concerned. I would, however, take the position that vendor-specific container extensions should be disabled by default and explicitly enabled by those making the conscious choice to use those extensions. This is the typical vendor extension pattern I have encountered, best promotes portability (if that is your goal), and is I believe the most responsible vendor choice. I'm interested to understand if/why you think otherwise. Especially if your extension implementation results in core Java platform manageability features like the LoggingMXBean no longer being viable ("Don't expose the platform LoggingMXBean over management", https://issues.jboss.org/browse/AS7-2185), it seems most responsible to make use of that extension a conscious choice. Regards, Scott -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira