[ https://issues.jboss.org/browse/JBIDE-19441?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19441: ------------------------------------- So it seems what is happening is as follows: The wizard (whether dynamic web or JPA project) gets a list of fixed facets. For Dynamic web, this is Java and jst.web. For JPA project, it's Java and jpt.jpa. It then gets a list of default facets for our runtime. For wildfly, as6, and all previous, we typically just list the default Java version. But for eap6.1, we specifically list a version of each facet. Why? because our EAP 6.1+ runtime expresses 'support' for higher facets even when we'd like the default to be a lower version. This is so users can upversion to higher spec without issue. Why does this work for dynamic web project on eap6.1+ but not for JPA? Because the framework will automatically remove any facets that 'conflict' with the primary / fixed facets. In the case of a dynamic web project, the fixed facet is jst.web, and so all the others (app-client, ejb, ear, etc) all conflict and are removed. In the case of JPA, none of our defaults conflict with the JPA facet individually; they only conflict with each other. So it adds all of our default facets to the default config, and removes none of them (since none conflict). I'll be looking into a solution. -- This message was sent by Atlassian JIRA (v6.3.11#6341)