[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=13420708#comment-13420708 ] 

Brian Stansberry commented on WFLY-8920:
----------------------------------------

I believe there's some other ejb3 subsystem setting that has a semantic similar to what we see here. I forget what it is; TBH I thought this JIRA was about it but I see now this is a new config item.

Found it. It's here:

https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJBDefaultSecurityDomainWriteHandler.java

That OSH updates the internal state of a DeploymentUnitProcessor. That means future deployments (or a redeploy) will pick up the new value, but existing deployments do not.

There may be others as well; there are a few "default xyx" settings in the subsystem.

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