[JBoss JIRA] (WFCORE-332) Allow RestartParentXXXHandlers to handle resources with multiple services
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-332?page=com.atlassian.jira.plugin... ]
Brian Stansberry resolved WFCORE-332.
-------------------------------------
Resolution: Won't Do
The RestartParentXXXHandlers are there to support what I now see as an anti-pattern -- creating resources that are nothing but config chunks for a parent. Complex attributes on the real resource should be used. So I'd rather put energy into that than into enhancing RestartParent.
> Allow RestartParentXXXHandlers to handle resources with multiple services
> -------------------------------------------------------------------------
>
> Key: WFCORE-332
> URL: https://issues.jboss.org/browse/WFCORE-332
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Richard Achmatowicz
> Assignee: Jason Greene
> Priority: Minor
>
> I'd like to use RestartParentWriteAttributeHandler to allow handling of attributes which, when updated, case a restart of only the services installed by their parent resource. These are really useful classes and solve a commonly encountered problem.
> However, the resource I want to restart involves four services, and it appears that RestartParentWriteAttriubuteHandler assumes that for every parent key name, there is only a single service registered.
> If we had the private methods:
> ServiceName[] getParentServiceNames(PathAddress address)
> boolean areParentServicesInstalled(ServiceName[] names)
> void removeServices(OperationContext context, ServiceNames[] names, ModelNode parentModel)
> this could be made to work for more general resources.
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ELY-1391) Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser.
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1391?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev commented on ELY-1391:
------------------------------------
[~honza889] I've checked all elements in elytron-1_0.xsd and compared them to the parser. I've found two issues (see PR). I'm not 100% sure about removing "credential-store" from XSD so please check if that is correct. Another mismatch which I found is that "File-backed realm elements" are present in elytron-1_0.xsd but not in the latest version of the parser which is expected.
> Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser.
> ----------------------------------------------------------------------------------
>
> Key: ELY-1391
> URL: https://issues.jboss.org/browse/ELY-1391
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Ilia Vassilev
> Assignee: Ilia Vassilev
>
> Check if all elements in elytron-1_0.xsd are parsed correctly in ElytronXmlParser and vice versa.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3346) Upgrade WildFly Elytron Tool to 1.0.2.Final
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3346?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-13417 to WFCORE-3346:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3346 (was: JBEAP-13417)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
> Upgrade WildFly Elytron Tool to 1.0.2.Final
> -------------------------------------------
>
> Key: WFCORE-3346
> URL: https://issues.jboss.org/browse/WFCORE-3346
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.5.Final
>
>
> There are no changes to the tool this release however the tool's jar also contains WildFly Elytron so this upgrade is just to bring the two in sync.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ELY-1246) The elytron-1_0.xsd has elements the parser does not accept
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1246?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev edited comment on ELY-1246 at 10/6/17 2:38 PM:
-------------------------------------------------------------
allow-sasl-mechanisms, allow-all-sasl-mechanisms and forbid-sasl-mechanisms are removed with PR https://github.com/wildfly-security/wildfly-elytron/pull/883
was (Author: ivassile):
allow-sasl-mechanisms, allow-all-sasl-mechanisms and forbid-sasl-mechanisms are removed
> The elytron-1_0.xsd has elements the parser does not accept
> -----------------------------------------------------------
>
> Key: ELY-1246
> URL: https://issues.jboss.org/browse/ELY-1246
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: James Perkins
> Assignee: Ilia Vassilev
>
> There are elements in the {{elytron-1_0.xsd}} that the parser does not accept. While I didn't check them all here are at least a few that are in the XSD that the parser will reject:
> * {{allow-sasl-mechanisms}}
> * {{allow-all-sasl-mechanisms}}
> * {{forbid-sasl-mechanisms}}
> This may be all of them, but it should likely be validated that those are the only ones.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month