[jboss-jira] [JBoss JIRA] (WFLY-12299) More fine grain dependency for galleon basic layers

[Jean Francois Denise (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13763861#comment-13763861 ] 

Jean Francois Denise commented on WFLY-12299:
---------------------------------------------

The current xxx-server is not very well formalized. It is a mix of WildFly server and "feature server" (such as web-server or core-server).

We have base-server (root resource and default public interface), core-server (an aggregation of the main features core-feature pack is expected to offer), web-server (a servlet container).

The server aspect of "base-server" meant that a WildFly server would be able to start when provisioning this layer. There is no "server" aspect, no entry point open for interaction.

The server aspect of "core-server" meant that a WildFly server offering the expected "management" feature would be provisioned. It could have been named "management-support" or "core-support". There is a "server" aspect, the management interface. This entry-point is not bound to the "core-server", it is the "management" layer that brings it, so provisioning "management" with any other layer would bring a "management server".

The server aspect of "web-server" meant both an aggregation of all features expected by a servlet container (ee, naming, deployment scanner) and the servlet server.

The jaxrs-server vs jaxrs is to be consistent with other decorators, but if jaxrs is not usable at all without a servlet container, it is implicit that the webserver is needed. The scanner can be explicitly excluded from the web-server, it is an optional dependency.

Questions on the servers you listed. Having the "xxx-server" layer seems to help separate use-cases when defining new layers.

"ejb-server"

Do you see splitting the ejb features into multiple layers, eg: ejb-common (dependency for other layers, eg: timers), ejb-session, ejb-mdb? We could still imagine a web-server+ejb-session kind of provisioned server.

The ejb-server would depend on ejb-session, configure a remote-connector, enable remote-naming, depend on undertow (no servlet support) + optionally iiop layer. 

"mdb-server"

Do you see it as something like the ejb-mdb + jms-activemq + resource-adapters layer?

"batch-server"

>From what I read, batch needs to be explicitly called. What would be the entry-point? Could be a servlet, jsf, ... So shouldn't it be a "batch" layer provisioned with another server that has the entry-point? eg: jsf+batch

> More fine grain dependency for galleon basic layers
> ---------------------------------------------------
>
>                 Key: WFLY-12299
>                 URL: https://issues.jboss.org/browse/WFLY-12299
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Build System
>            Reporter: Jean Francois Denise
>            Assignee: Jean Francois Denise
>            Priority: Major
>
> Having basic layers to only depend on the layers (and features) they do require will offer more flexibility than depending on web-server layer.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)