[JBoss JIRA] (WFCORE-321) Spurious server dirs created when directory-grouping="by-type" is set
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-321?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-89 to WFCORE-321:
---------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-321 (was: WFLY-89)
Component/s: Domain Management
(was: Domain Management)
> Spurious server dirs created when directory-grouping="by-type" is set
> ---------------------------------------------------------------------
>
> Key: WFCORE-321
> URL: https://issues.jboss.org/browse/WFCORE-321
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Priority: Minor
>
> Add directory-grouping="by-type" to the <host><servers> element in the stock host.xml and run domain.sh. The following empty directories are created:
> $JBOSS_HOME/domain/servers/server-one
> $JBOSS_HOME/domain/servers/server-two
> The content that would normally be in those dirs if directory-grouping="by-type" wasn't set appears to all be going where it should (e.g. under domain/data, domain/log etc) so the only issue here is the empty directories.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-322) Allow restart of management interface services via allow-resource-restart header
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-322?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-2254 to WFCORE-322:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-322 (was: WFLY-2254)
Component/s: Domain Management
(was: Domain Management)
> Allow restart of management interface services via allow-resource-restart header
> --------------------------------------------------------------------------------
>
> Key: WFCORE-322
> URL: https://issues.jboss.org/browse/WFCORE-322
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Priority: Minor
>
> The management interface resources seem like good candidates for allow-resource-restart handling. A restart of the services should not propagate through a broad range of dependent services, while an admin could quite reasonably want to update these without taking a server outage.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-323) Validate composite operation steps just before executing them
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-323?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1019 to WFCORE-323:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-323 (was: WFLY-1019)
Component/s: Domain Management
(was: Domain Management)
> Validate composite operation steps just before executing them
> -------------------------------------------------------------
>
> Key: WFCORE-323
> URL: https://issues.jboss.org/browse/WFCORE-323
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Labels: EAP
>
> Say we have a composite operation with 2 steps:
> 1) /extension=org.jboss.as.messaging:add
> 2) /subsystem=messaging:add
> This will fail:
> Failed to execute batch: JBAS014739: No handler for add at address
> [("subsystem" => "messaging")]
> This fails because at the time of validation the /subsystem=messaging:add is not valid.
> To illustrate, the execution order is
> Validate 1-2
> 1
> 2
> A possible solution is to convert this to the following:
> V1
> 1
> V2 (works now because 1 has registered the subsystem API)
> 2
> I think that should work but it's a very complex area, particularly in a managed domain, so it's not at all certain this would prove feasible.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-317) Failed to start server when -backup -cached-dc are used together
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-317?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-773 to WFCORE-317:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-317 (was: WFLY-773)
Component/s: Domain Management
(was: Domain Management)
> Failed to start server when -backup -cached-dc are used together
> ----------------------------------------------------------------
>
> Key: WFCORE-317
> URL: https://issues.jboss.org/browse/WFCORE-317
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Rok Bertoncelj
>
> When starting a slave host controller with *-backup -cached-dc* at the same time, the servers fail to start. Tested with 7.1.1.Final and 7.1.2.Final-SNAPSHOT today.
> Also tried starting only with -backup first (starts OK) and then for the second time with both options, to make sure that cached configuration is already present if it would help, but it didn't.
> Host controller should determine availability of domain controller and either backup domain configuration or use the cached one if domain controller is unavailable.
> {code}
> 10:35:36,093 INFO [org.jboss.modules] (main) JBoss Modules version 1.1.1.GA
> 10:35:36,176 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.2.GA
> 10:35:36,225 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" starting
> 10:35:36,612 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010930: Cannot load the domain model using using --backup
> 10:35:36,617 INFO [org.xnio] (MSC service thread 1-6) XNIO Version 3.0.3.GA
> 10:35:36,631 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.0.3.GA
> 10:35:36,649 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 3.2.4.GA
> 10:35:36,970 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010907: Failed to start server (server-one): java.util.NoSuchElementException: No child 'server-group' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:298) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.dmr.ModelNode.require(ModelNode.java:812) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.host.controller.ModelCombiner.<init>(ModelCombiner.java:139) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.createManagedServer(ServerInventoryImpl.java:474) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:160) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:150) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:521) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler.cleanStartServers(StartServersHandler.java:114) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler.access$300(StartServersHandler.java:50) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler$1.execute(StartServersHandler.java:94) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.executeDirect(PrepareStepHandler.java:122) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:74) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.startServers(DomainModelControllerService.java:443) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:403) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> 10:35:36,989 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:29999
> 10:35:37,015 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010907: Failed to start server (server-two): java.util.NoSuchElementException: No child 'server-group' exists
> at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:298) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.dmr.ModelNode.require(ModelNode.java:812) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.host.controller.ModelCombiner.<init>(ModelCombiner.java:139) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.createManagedServer(ServerInventoryImpl.java:474) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:160) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:150) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:521) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler.cleanStartServers(StartServersHandler.java:114) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler.access$300(StartServersHandler.java:50) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.operations.StartServersHandler$1.execute(StartServersHandler.java:94) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.executeDirect(PrepareStepHandler.java:122) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:74) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.startServers(DomainModelControllerService.java:443) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:403) [jboss-as-host-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> 10:35:37,082 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" (Host Controller) started in 1249ms - Started 11 of 11 services (0 services are passive or on-demand)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-318) module.xml schema checking should log errors when it encounters them
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-318?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-832 to WFCORE-318:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-318 (was: WFLY-832)
Component/s: Domain Management
(was: Domain Management)
> module.xml schema checking should log errors when it encounters them
> ---------------------------------------------------------------------
>
> Key: WFCORE-318
> URL: https://issues.jboss.org/browse/WFCORE-318
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Tom Fonteyne
> Assignee: Brian Stansberry
> Priority: Minor
>
> When defining a JDBC driver, we made a syntax error in the module.xml
> <resources>
> <resource-root path="driver.jar"/>
> </resoruces>
> Note the misspelled closing tag "</resoruces>"
> The driver did not get loaded (logically) but no error message was logged in server.log about this
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-319) Metrics/operations missing in platform mbean core-service
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-319?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-857 to WFCORE-319:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-319 (was: WFLY-857)
Component/s: Domain Management
(was: Domain Management)
> Metrics/operations missing in platform mbean core-service
> ---------------------------------------------------------
>
> Key: WFCORE-319
> URL: https://issues.jboss.org/browse/WFCORE-319
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Rupp
> Labels: rhq
>
> The platform mbean(s) exposes more metrics that what is currently available at core-service=platform-mbean
> - Active Thread Count
> - Active Thread Group Count
> - JVM Free memory
> - JVM Total memory
>
> OS metrics -- java.lang:type=OperatingSystem
> - Free Physical Memory -- FreePhysicalMemorySize
> - Free Swap Memory -- FreeSwapSpaceSize
> - Process CPU Time -- ProcessCpuTime
> - Committed Virtual Memory -- CommittedVirtualMemorySize
> - open files --OpenFileDescriptorCount
> Threading
> - SuspendedThreadCount
> - DeadLockedThreadCount
> Memory -- java.lang:type=Memory
> - operation to trigger gc -- gc
> And probably more
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-315) NPE executing domain operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-315?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1997 to WFCORE-315:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-315 (was: WFLY-1997)
Component/s: Domain Management
(was: Domain Management)
> NPE executing domain operation
> ------------------------------
>
> Key: WFCORE-315
> URL: https://issues.jboss.org/browse/WFCORE-315
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Emanuel Muckenhuber
>
> {noformat}
> [ERROR] Request
> [ERROR] {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "address" => [("server-group" => "*")],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] },
> [ERROR] {
> [ERROR] "address" => [
> [ERROR] ("host" => "master"),
> [ERROR] ("server" => "*")
> [ERROR] ],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] },
> [ERROR] {
> [ERROR] "address" => [("extension" => "*")],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] }
> [ERROR] ],
> [ERROR] "operation-headers" => {"roles" => "OPERATOR"}
> [ERROR] }
> {noformat}
> leads to
> {noformat}
> [Host Controller] 16:34:53,544 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-12) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.NullPointerException
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:167)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:181)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationSlaveStepHandler.addSteps(OperationSlaveStepHandler.java:108)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:201)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:124)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:103)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:257) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:142) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:154) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:96) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_17]
> [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_17]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:86) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> [Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> [Host Controller]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (WFCORE-314) Configure child resources as mandatory or its cardinality in ResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-314?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-2915 to WFCORE-314:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-314 (was: WFLY-2915)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: (was: 9.0.0.Beta1)
> Configure child resources as mandatory or its cardinality in ResourceDefinition
> -------------------------------------------------------------------------------
>
> Key: WFCORE-314
> URL: https://issues.jboss.org/browse/WFCORE-314
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Pedro Igor
>
> Currently, the ResourceDefinition does not provide a good way to configure a child resource as mandatory or even its cardinality. Instead of that, manual validations are required inside handlers.
> The idea is remove manual validations and let it be done automatically by the model.
> Considering the following example:
> {code:xml}
> <parent-resource>
> <child-resource/>
> </parent-resource>
> {code}
> Would be useful if we could mark the 'child-resource' above as mandatory. Or even:
> {code:xml}
> <parent-resource>
> <child-resource/>
> <child-resource/>
> <child-resource/>
> <child-resource/> <!-- This is invalid. Only 3 childs are supported. -->
> </parent-resource>
> {code}
> Where we can specify the cardinality for a child-resource so we can configure the min/max occurrences.
> I think the latter approach is more flexible and can be used to get a resource as mandatory or specify its number of occurrence.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months