[ https://issues.jboss.org/browse/AS7-1389?page=com.atlassian.jira.plugin.s... ] Scott Hasse commented on AS7-1389: ---------------------------------- Regarding point 5, I agree this is true as stated, although I don't understand why you would say "JBoss AS and its successor, WildFly, are not Java EE containers..." above. It seems clear to me that when deploying a JEE artifact they are JEE specification-compliant containers. I presume that EAP 7 will follow in the footsteps of EAP 4.x, 5.x and 6.x and obtain official specification compliance, the opportunity for which for JEE at least was hard fought and won by the Apache foundation and JBoss/RedHat. The enterprise customers I work with depend on that. To clarify, I believe the context of what we are discussing is container behavior when deploying JEE-specific artifacts such as ear and war files. In that context, I am still hard-pressed to find any EAP-provided extensions other than the third party logging APIs and implementations, so I don't understand what the "many" facilities are. But in any case what we are talking about is the logging implementation. Since in the context of a JEE deployment whether or not third party logging APIs and implementations are "good examples" of extensions overlaps somewhat with point 6, I can give you my perspective on that below. -- 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