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

[Brian Stansberry (Jira)]

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

Brian Stansberry commented on WFLY-12299:
-----------------------------------------

Back to "what makes a xxx-server"...  

I think it does work triggered by external activity of some sort or has some sort of internal trigger. It handles the triggering event, so its layer includes/depends on whatever is needed for that.

web-server
ejb-server (remote session beans; listens for requests)
mdb-server (pulls messages from a broker)
batch-server
messaging-server

If we limit ourselves to cases that involve deployments, then messaging-server comes off the list. (Which is fine; Artemis itself provides a server; wrapping it in WF for no users other than external clients is an anti-pattern.) Since they all involve deployments, they all get deployment-scanner just to keep it simple.

Then the other layers are either

1) dependencies of servers
2) "decorators" of one particular server (and thus can depend on it) -- e.g. jax-rs, webservices, jsf
3) "decorators" for potentially many servers (and thus don't depend on them) -- cdi, jpa, lots of stuff

And then a xxx-profile is a server + a set of decorators.

> 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)