[ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12299: ----------------------------------------- bstansberry 10 days ago Member @jfdenise Does this need to depend on this aggregation layer, as opposed to specific detail layers from servlet f-p? There are a few in this category. Here's what depends on web-server: {code} $ git grep "layer name=\"web-server\"" galleon-pack/src/main/resources/layers/standalone/cdi/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/h2-database/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jaxrs/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jms-activemq/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/jpa/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/observability/layer-spec.xml: <layer name="web-server"/> galleon-pack/src/main/resources/layers/standalone/resource-adapters/layer-spec.xml: <layer name="web-server"/> {code} Obviously jaxrs needs web-server. The others it's less obvious that HTTP is required. The advantage of doing it this way is for a servlet app with jpa support you can just say "jpa" instead of "web-server, jpa". And perhaps for compatibility reasons we have to leave it that way for the existing layers. But that doesn't apply to this 'transactions' one, since it is new. Apologies if we've discussed this and I've forgotten. The wildfly-dev "Wildfly layers" doesn't have any discussion, other than your initial post that stated it would work this way. -- This message was sent by Atlassian Jira (v7.12.1#712002)