[JBoss JIRA] (WFCORE-3252) provide better filtering of host-exclude for prior releases
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3252?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3252:
-------------------------------------
Fix Version/s: 4.0.0.Alpha4
(was: 4.0.0.Alpha3)
> provide better filtering of host-exclude for prior releases
> -----------------------------------------------------------
>
> Key: WFCORE-3252
> URL: https://issues.jboss.org/browse/WFCORE-3252
> Project: WildFly Core
> Issue Type: Enhancement
> Reporter: Ken Wills
> Assignee: Ken Wills
> Fix For: 4.0.0.Alpha4
>
>
> Currently a new domain controller connecting to a legacy slave will pass host-exclude values that the HostExcludeResourceDefinition enum on the slave doesn't understand.
> WFCORE-3226 provided a simple workaround fix to allow this to work via a transformer, but we should have a better mechanism to only send =< the slave version values from the enum, or something similar perhaps.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (ELY-1448) API Compatibility for org.wildfly.security.mechanism.MechanismUtil
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-1448:
-------------------------------------
Summary: API Compatibility for org.wildfly.security.mechanism.MechanismUtil
Key: ELY-1448
URL: https://issues.jboss.org/browse/ELY-1448
Project: WildFly Elytron
Issue Type: Bug
Components: API / SPI
Reporter: Darran Lofthouse
Priority: Blocker
Fix For: 1.2.0.Beta10
Backwards compatibility has been broken on the public handleCallbacks methods so this needs to be fixed.
However this class should not really be a public API, it has been picked up in the package as we have the AuthenticationMechanismException which does need to be public.
The entire class should be deprecated and the impl moved to a private package.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9559) JMXPropertyEditorsTestCase should use 1 deployment not 40
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-9559:
--------------------------------------
Summary: JMXPropertyEditorsTestCase should use 1 deployment not 40
Key: WFLY-9559
URL: https://issues.jboss.org/browse/WFLY-9559
Project: WildFly
Issue Type: Task
Components: JMX, Test Suite
Reporter: Brian Stansberry
Assignee: Kabir Khan
Priority: Minor
JMXPropertyEditorsTestCase does 40 different deployment operations, with each identical except for changing a deployment descriptor to configure xml for 1 mbean attribute. Then the test checks that value.
Do 1 deployment with 40 config items and then check them all. Eliminate 78 management ops (39 pairs of deploy/undeploy.)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9558) Eliminate redundant testing in JGroups and Infinispan subsystem tests
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-9558:
--------------------------------------
Summary: Eliminate redundant testing in JGroups and Infinispan subsystem tests
Key: WFLY-9558
URL: https://issues.jboss.org/browse/WFLY-9558
Project: WildFly
Issue Type: Task
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
The JGroups and Infinispan subsystems have subclasses of AbstractSubsystemBaseTest that include @Test method that essentially duplicate parts of what the superclass testSubsystem does. These subclasses execute the test for numerous xml versions, so the duplication isn't just run once. So, remove that.
In the infinispan case removing it saves about 10s on my laptop, but more importantly it saves about a minute on Windows runs on ci.wildfly.org. The long execution time on CI is what drew my attention to this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2145) Kie-Spring: listeners on KieSession not called when batch is used
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2145?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-2145:
--------------------------------
Sprint: BxMS70-Iteration7
> Kie-Spring: listeners on KieSession not called when batch is used
> -----------------------------------------------------------------
>
> Key: DROOLS-2145
> URL: https://issues.jboss.org/browse/DROOLS-2145
> Project: Drools
> Issue Type: Bug
> Components: integration
> Reporter: Mario Fusco
> Assignee: Mario Fusco
>
> Description of problem:
> When using the following configuration in Spring context, the listener is not called when the rule triggered by the batch fires:
> <kie:ksession name="ksession1">
> <kie:ruleRuntimeEventListener ref="mock-wm-listener"/>
> <kie:batch>
> <kie:insert-object ref="person"/>
> <kie:fire-all-rules/>
> </kie:batch>
> </kie:ksession>
> The listener is triggered when a fact is inserted into the KieSession and fireAllRules() called in the test code (not in the batch).
> The fact seems to be inserted into WM and rules fire when the batch is used. This leads to a suggestion that kie-spring might register listeners after it executes the batch (but I have not verified it).
> Please see PR with unit test for details.
> Version-Release number of selected component (if applicable):
> BRMS 6.2.1
> How reproducible:
> always
> Steps to Reproduce:
> 1. run org.kie.spring.KieSpringListenersBatchTest
> Actual results:
> The test fails.
> Expected results:
> The test succeeds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2145) Kie-Spring: listeners on KieSession not called when batch is used
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-2145:
-----------------------------------
Summary: Kie-Spring: listeners on KieSession not called when batch is used
Key: DROOLS-2145
URL: https://issues.jboss.org/browse/DROOLS-2145
Project: Drools
Issue Type: Bug
Components: integration
Reporter: Mario Fusco
Assignee: Mario Fusco
Description of problem:
When using the following configuration in Spring context, the listener is not called when the rule triggered by the batch fires:
<kie:ksession name="ksession1">
<kie:ruleRuntimeEventListener ref="mock-wm-listener"/>
<kie:batch>
<kie:insert-object ref="person"/>
<kie:fire-all-rules/>
</kie:batch>
</kie:ksession>
The listener is triggered when a fact is inserted into the KieSession and fireAllRules() called in the test code (not in the batch).
The fact seems to be inserted into WM and rules fire when the batch is used. This leads to a suggestion that kie-spring might register listeners after it executes the batch (but I have not verified it).
Please see PR with unit test for details.
Version-Release number of selected component (if applicable):
BRMS 6.2.1
How reproducible:
always
Steps to Reproduce:
1. run org.kie.spring.KieSpringListenersBatchTest
Actual results:
The test fails.
Expected results:
The test succeeds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months