[jboss-jira] [JBoss JIRA] (WFLY-8920) Adding application-security-domain in EJB subsystem requires server reload

[Brian Stansberry (JIRA)]

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

Brian Stansberry edited comment on WFLY-8920 at 6/13/17 11:55 AM:
------------------------------------------------------------------

I have my doubts this is a bug.

You've deployed the app. It's deployed using the resources available to it at that time. Now some other resources are created, and the expectation is the already deployed app should automagically take advantage of those new resources.

What happens if you deploy a new app, after the /subsystem=ejb3/application-security-domain=other:add but without a reload? I believe it will pick up ApplicationDomain.

-I believe this behavior is intentional; IIRC this has come up in the past and been confirmed as such.-

So: why not just say "reload-required" anyway, just in case? That's because if a capability (which there eventually will be here) goes reload-required, then further changes to that cap or caps that depend on it will no longer execute runtime changes. So, adding "reload-required" is going to have side effects and isn't something we should just do.


was (Author: brian.stansberry):
I have my doubts this is a bug.

You've deployed the app. It's deployed using the resources available to it at that time. Now some other resources are created, and the expectation is the already deployed app should automagically take advantage of those new resources.

What happens if you deploy a new app, after the /subsystem=ejb3/application-security-domain=other:add but without a reload? I believe it will pick up ApplicationDomain.

I believe this behavior is intentional; IIRC this has come up in the past and been confirmed as such.

So: why not just say "reload-required" anyway, just in case? That's because if a capability (which there eventually will be here) goes reload-required, then further changes to that cap or caps that depend on it will no longer execute runtime changes. So, adding "reload-required" is going to have side effects and isn't something we should just do.

> Adding application-security-domain in EJB subsystem requires server reload
> --------------------------------------------------------------------------
>
>                 Key: WFLY-8920
>                 URL: https://issues.jboss.org/browse/WFLY-8920
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 11.0.0.Beta1
>            Reporter: Ondrej Lukas
>            Assignee: Ingo Weiss
>            Priority: Critical
>
> When application-security-domain is added in EJB subsystem then it is not used until server is reloaded. However CLI command does not set server to {{reload-required}} state, see:
> {code}
> /subsystem=ejb3/application-security-domain=other:add(security-domain=ApplicationDomain)
> {"outcome" => "success"}
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)