May 2018 - jboss-jira - Jboss List Archives

[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 reassigned WFCORE-323: --------------------------------------- Assignee: Brian Stansberry > 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: 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 (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10341) Enable EclipseLink integration tests for Java 10

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10341?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10341: -------------------------------- Description: Disabled EclipseLink testing due to WFLY-10177 which reports test failures only on JDK10. When EclipseLink 2.7.2 is shipped and supports Java 10, re-enable EclipseLink testing. was: Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. > Enable EclipseLink integration tests for Java 10 > ------------------------------------------------ > > Key: WFLY-10341 > URL: https://issues.jboss.org/browse/WFLY-10341 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > > Disabled EclipseLink testing due to WFLY-10177 which reports test failures only on JDK10. When EclipseLink 2.7.2 is shipped and supports Java 10, re-enable EclipseLink testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10341) Enable EclipseLink integration tests for Java 10

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10341?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10341: -------------------------------- Summary: Enable EclipseLink integration tests for Java 10 (was: Enable OpenJPA integration tests for Java 10) > Enable EclipseLink integration tests for Java 10 > ------------------------------------------------ > > Key: WFLY-10341 > URL: https://issues.jboss.org/browse/WFLY-10341 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > > Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10341) Enable OpenJPA integration tests for Java 10

by Scott Marlow (JIRA)

Scott Marlow created WFLY-10341: ----------------------------------- Summary: Enable OpenJPA integration tests for Java 10 Key: WFLY-10341 URL: https://issues.jboss.org/browse/WFLY-10341 Project: WildFly Issue Type: Enhancement Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Priority: Minor Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1148) Non runtime-only operation can be invoked in domain servers

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1148?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1148: ---------------------------------------- Assignee: (was: Brian Stansberry) > Non runtime-only operation can be invoked in domain servers > ----------------------------------------------------------- > > Key: WFCORE-1148 > URL: https://issues.jboss.org/browse/WFCORE-1148 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 2.0.2.Final > Reporter: Jeff Mesnil > Priority: Minor > Labels: domain-mode > > While working on WFLY-5418, I noticed that non runtime-only operations can be invoked on domain servers under /host=X/server=Y/... > The operation is not listed in read-operation-names, read-resource-description, etc. but invoking it is still possible. > Brian confirmed that this is a bug and the operation should not be executed. > Steps to reproduce: > * remove the runtimeOnly flag in org.jboss.as.ejb3.subsystem.deployment.MessageDrivenBeanResourceDefinition#registerOperations > * deploy the quickstart helloworld-mdb > * the start-delivery (and stop-delivery) operations are not listed in /host=master/server=server-one/deployment=wildfly-helloworld-mdb.war/subsystem=ejb3/message-driven-bean=HelloWorldQueueMDB:read-operation-names > * But the method can be invoked by executing: > {noformat} > [domain@localhost:9990 /] /host=master/server=server-one/deployment=wildfly-helloworld-mdb.war/subsystem=ejb3/message-driven-bean=HelloWorldQueueMDB:start-delivery ain@localhost:9990 /] > { > "outcome" => "success", > "result" => undefined > } > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2687) Expose the current step operation's name and parameters via the OperationContext

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2687?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2687: ---------------------------------------- Assignee: (was: Brian Stansberry) > Expose the current step operation's name and parameters via the OperationContext > -------------------------------------------------------------------------------- > > Key: WFCORE-2687 > URL: https://issues.jboss.org/browse/WFCORE-2687 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > > Remove the need to pass the 'operation' ModelNode to a method for it to be able to learn about the currently effective operation. > OperationContext already exposes getCurrentAddress(). Add getCurrentOperationName() and getCurrentOperationParameter(String name). > The latter returns null if !operation.has(name) otherwise it returns whatever the node was. Or perhaps return undefined with an overloaded variant with a boolean param that lets the caller turn on getting null. > The getCurrentOperationParameter should reject 'name', 'address', 'operation-headers' etc as legal param names; only expose true parameters. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3107) Allow slave hosts to ignore missing RBAC config resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3107?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3107: ------------------------------------- Labels: domain-mode (was: ) > Allow slave hosts to ignore missing RBAC config resources > --------------------------------------------------------- > > Key: WFCORE-3107 > URL: https://issues.jboss.org/browse/WFCORE-3107 > Project: WildFly Core > Issue Type: Sub-task > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Labels: domain-mode > > Part of parent issue whereby slaves can ignore missing RBAC constraint resources for write requests coming from the DC. > If the DC sent the request, then the address is ok overall. So if it's missing on the slave that means the slave doesn't have that constraint registered and doesn't need to handle the op. > This fix could possibly be backported to the 2.1.x and to EAP 6.4.x in lieu of adding transformers as part of the parent issue. In the case of 2.1.x it also allows slaves to ignore the related extension even if the code for it is present (which is only a minor benefit.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2688) RestartParentWriteAttributeHandler.isResourceServiceRestartAllowed should check the AttributeDefinition

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2688?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2688: ---------------------------------------- Assignee: (was: Brian Stansberry) > RestartParentWriteAttributeHandler.isResourceServiceRestartAllowed should check the AttributeDefinition > ------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2688 > URL: https://issues.jboss.org/browse/WFCORE-2688 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > > Besides checking with the context as to whether the allow-resource-service-restart header is set, if there is an AD available, it should be checked. > At one stroke this will turn off this ability for everything that doesn't specifically allow it. > Needs checks though to fix attributes that are meant to allow this but don't say so. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2850) AbstractRuntimeOnlyHandler should not add its step on a profile=* resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2850?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2850: ------------------------------------------ My WFCORE-2850 branch has the remaining change, but trying that on PR #2426 resulted in unexpected failures, hence my comment ^^^. > AbstractRuntimeOnlyHandler should not add its step on a profile=* resource > --------------------------------------------------------------------------- > > Key: WFCORE-2850 > URL: https://issues.jboss.org/browse/WFCORE-2850 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > The child resources of /profile=* do not have a runtime behind them, so AbstractRuntimeOnlyStepHandler should not add its Stage.RUNTIME step if the target resources is in that tree. > This will make it possible to use this class if as part of WFCORE-389 we lift the (currently unenforced) restriction on adding runtime-only ops to profile resources in order to have the DC roll them out to relevant servers. It's particular important in the context of the related WFCORE-2815, which would result in the current AbstractRuntimeOnlyStepHandler impl failing if used on a profile resource, since the step it adds would be rejected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10340) Enable OpenJPA integration tests for Java 10

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10340?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-10340: -------------------------------- Description: Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. was: Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable OpenJPA testing. > Enable OpenJPA integration tests for Java 10 > -------------------------------------------- > > Key: WFLY-10340 > URL: https://issues.jboss.org/browse/WFLY-10340 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Minor > > Disable OpenJPA testing due to WFLY-10177 which reports test failures only on JDK10. When OpenJPA supports Java 10, re-enable org.jboss.as.test.compat.jpa.openjpa.OpenJPASharedModuleProviderTestCase. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2018