[ https://issues.jboss.org/browse/WFLY-10847?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10847: ----------------------------------------- EARs are used all sorts of ways and I don't think you can assume a particular pattern dominates and others are edge cases. The wikipedia description of them[1] is useful: {quote} a file format used by Java EE for packaging one or more modules into a single archive so that the deployment of the various modules onto an application server happens simultaneously and coherently {quote} As part of "coherently" I'd included the shared classloading rules that EE specifies for EARs. Anyone who wants to take advantage of that simultaneous and coherent deployment model might use an ear. One thought I have though is that for a loooonnnng time now EE supports packaging EJBs in wars, no longer requiring an EAR. And of course using CDI managed beans in a webapp doesn't require an EAR. So some of the original ancient use case for an ear is no longer applicable, increasing the probability that someone using an EAR today is doing so because they are deploying multiple wars. That doesn't answer whether those folks conceive of those multiple wars as a single service. I figure some do some don't. [~bmaxwell] Any thoughts on this? [1] https://en.wikipedia.org/wiki/EAR_(file_format) -- This message was sent by Atlassian JIRA (v7.5.0#75005)