[JBoss JIRA] (DROOLS-742) DecisionTableXLSToDecisionTableGuidedConverterTest fails on jdk8
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-742?page=com.atlassian.jira.plugin... ]
Michael Anstis reassigned DROOLS-742:
-------------------------------------
Assignee: Michael Anstis (was: Mario Fusco)
> DecisionTableXLSToDecisionTableGuidedConverterTest fails on jdk8
> ----------------------------------------------------------------
>
> Key: DROOLS-742
> URL: https://issues.jboss.org/browse/DROOLS-742
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.2.0.Final
> Reporter: Tibor Zimányi
> Assignee: Michael Anstis
> Priority: Minor
>
> Failing test is from drools-wb repo.
> Test methods testConditions() and testConditionsIndexedParameters() fails on jdk8.
> XLS files used in these methods contain multiple parameters column (column with more parameters than one). When XLS is parsed, these parameters are transformed into child columns of BRLConditionColumn. In ParameterUtilities class is method extractTemplateKeys. This method extracts params from preprocessed original string from XLS table cell containing parameters. But because the method uses HashSet as return value, the ordering of parameters cannot be determined (in HashSet, the order of items can be different than the order in which the items were inserted).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-747) declared window, type length(1), do actually contain more than 1 object (with reteoo)
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-747?page=com.atlassian.jira.plugin... ]
Matteo Mortari updated DROOLS-747:
----------------------------------
Attachment: 20150323.DROOLS-747-reproducer.zip
attaching the reproducer.
> declared window, type length(1), do actually contain more than 1 object (with reteoo)
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-747
> URL: https://issues.jboss.org/browse/DROOLS-747
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
> Attachments: 20150323.DROOLS-747-reproducer.zip
>
>
> h5. Premise
> I know reteoo is progressively being deprecated, but I think until is there is helpful for A/B testing of possible leaks comparing with phreak (like it happened during 610Final) so reporting this bug.
> h5. Executive summary
> Declaring a window of type length (1) should always contain 1 object.
> h5. Details
> With reference to attached reproducer.
> Given the following knowledge base:
> {code}
> global java.util.concurrent.atomic.AtomicLong globalCounter;
> declare Measurement
> @role(event)
> end
> declare window lastMeasurement
> Measurement() over window:length( 1 ) // from entry-point DEFAULT
> end
> rule "IFF the last Measurement that I know of, is of ID color, increment the counter"
> no-loop
> when
> Measurement( id == "color" ) from window lastMeasurement
> then
> globalCounter.incrementAndGet();
> end
> {code}
> The goal is: IFF the last Measurement that I know of, is of ID "color", increment the counter. Please notice you ought to separate the window being just on Measurement, in order to know the last Measurement regardless of the ID, and then you have a rule acting on the declared window, to check IFF this last Measurement, is actually of ID "color".
> Now assuming you just have created the session and the following increment/insert/fire:
> {code}
> AtomicLong globalCounter = new AtomicLong(0);
> session.setGlobal("globalCounter", globalCounter);
> session.fireAllRules();
> assertEquals("no data, still 0", 0, globalCounter.get());
> LOG.info("Now running data");
> clock.advanceTime(1, TimeUnit.MINUTES);
> Measurement mRed= new Measurement("color", "red");
> session.insert(mRed);
> Measurement mGreen= new Measurement("color", "green");
> session.insert(mGreen);
> Measurement mBlue= new Measurement("color", "blue");
> session.insert(mBlue);
> session.fireAllRules();
> LOG.info("Final checks");
> assertEquals("win lenght =1 was: ", 1, globalCounter.get());
> {code}
> At the end you should have the global counter with value = 1, because we inserted 3 events of type Measurement, but the declared window lastMeasurement should reference only {{mBlue}}, which should be later picked by the rule because the ID is "color", and increment the counter by 1.
> This works with phreak, it does not work with reteo.
> phreak globalCounter = 1 : OK
> reteoo globalCounter = 3 : FAIL.
> Could you kindly advise, please?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-747) declared window, type length, do actually contain more than 1 object (with reteoo)
by Matteo Mortari (JIRA)
Matteo Mortari created DROOLS-747:
-------------------------------------
Summary: declared window, type length, do actually contain more than 1 object (with reteoo)
Key: DROOLS-747
URL: https://issues.jboss.org/browse/DROOLS-747
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.2.0.Final
Reporter: Matteo Mortari
Assignee: Mario Fusco
h5. Premise
I know reteoo is progressively being deprecated, but I think until is there is helpful for A/B testing of possible leaks comparing with phreak (like it happened during 610Final) so reporting this bug.
h5. Executive summary
Declaring a window of type length (1) should always contain 1 object.
h5. Details
With reference to attached reproducer.
Given the following knowledge base:
{code}
global java.util.concurrent.atomic.AtomicLong globalCounter;
declare Measurement
@role(event)
end
declare window lastMeasurement
Measurement() over window:length( 1 ) // from entry-point DEFAULT
end
rule "IFF the last Measurement that I know of, is of ID color, increment the counter"
no-loop
when
Measurement( id == "color" ) from window lastMeasurement
then
globalCounter.incrementAndGet();
end
{code}
The goal is: IFF the last Measurement that I know of, is of ID "color", increment the counter. Please notice you ought to separate the window being just on Measurement, in order to know the last Measurement regardless of the ID, and then you have a rule acting on the declared window, to check IFF this last Measurement, is actually of ID "color".
Now assuming you just have created the session and the following increment/insert/fire:
{code}
AtomicLong globalCounter = new AtomicLong(0);
session.setGlobal("globalCounter", globalCounter);
session.fireAllRules();
assertEquals("no data, still 0", 0, globalCounter.get());
LOG.info("Now running data");
clock.advanceTime(1, TimeUnit.MINUTES);
Measurement mRed= new Measurement("color", "red");
session.insert(mRed);
Measurement mGreen= new Measurement("color", "green");
session.insert(mGreen);
Measurement mBlue= new Measurement("color", "blue");
session.insert(mBlue);
session.fireAllRules();
LOG.info("Final checks");
assertEquals("win lenght =1 was: ", 1, globalCounter.get());
{code}
At the end you should have the global counter with value = 1, because we inserted 3 events of type Measurement, but the declared window lastMeasurement should reference only {{mBlue}}, which should be later picked by the rule because the ID is "color", and increment the counter by 1.
This works with phreak, it does not work with reteo.
phreak globalCounter = 1 : OK
reteoo globalCounter = 3 : FAIL.
Could you kindly advise, please?
Thanks
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (DROOLS-747) declared window, type length(1), do actually contain more than 1 object (with reteoo)
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-747?page=com.atlassian.jira.plugin... ]
Matteo Mortari updated DROOLS-747:
----------------------------------
Summary: declared window, type length(1), do actually contain more than 1 object (with reteoo) (was: declared window, type length, do actually contain more than 1 object (with reteoo))
> declared window, type length(1), do actually contain more than 1 object (with reteoo)
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-747
> URL: https://issues.jboss.org/browse/DROOLS-747
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.2.0.Final
> Reporter: Matteo Mortari
> Assignee: Mario Fusco
>
> h5. Premise
> I know reteoo is progressively being deprecated, but I think until is there is helpful for A/B testing of possible leaks comparing with phreak (like it happened during 610Final) so reporting this bug.
> h5. Executive summary
> Declaring a window of type length (1) should always contain 1 object.
> h5. Details
> With reference to attached reproducer.
> Given the following knowledge base:
> {code}
> global java.util.concurrent.atomic.AtomicLong globalCounter;
> declare Measurement
> @role(event)
> end
> declare window lastMeasurement
> Measurement() over window:length( 1 ) // from entry-point DEFAULT
> end
> rule "IFF the last Measurement that I know of, is of ID color, increment the counter"
> no-loop
> when
> Measurement( id == "color" ) from window lastMeasurement
> then
> globalCounter.incrementAndGet();
> end
> {code}
> The goal is: IFF the last Measurement that I know of, is of ID "color", increment the counter. Please notice you ought to separate the window being just on Measurement, in order to know the last Measurement regardless of the ID, and then you have a rule acting on the declared window, to check IFF this last Measurement, is actually of ID "color".
> Now assuming you just have created the session and the following increment/insert/fire:
> {code}
> AtomicLong globalCounter = new AtomicLong(0);
> session.setGlobal("globalCounter", globalCounter);
> session.fireAllRules();
> assertEquals("no data, still 0", 0, globalCounter.get());
> LOG.info("Now running data");
> clock.advanceTime(1, TimeUnit.MINUTES);
> Measurement mRed= new Measurement("color", "red");
> session.insert(mRed);
> Measurement mGreen= new Measurement("color", "green");
> session.insert(mGreen);
> Measurement mBlue= new Measurement("color", "blue");
> session.insert(mBlue);
> session.fireAllRules();
> LOG.info("Final checks");
> assertEquals("win lenght =1 was: ", 1, globalCounter.get());
> {code}
> At the end you should have the global counter with value = 1, because we inserted 3 events of type Measurement, but the declared window lastMeasurement should reference only {{mBlue}}, which should be later picked by the rule because the ID is "color", and increment the counter by 1.
> This works with phreak, it does not work with reteo.
> phreak globalCounter = 1 : OK
> reteoo globalCounter = 3 : FAIL.
> Could you kindly advise, please?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4454) Convert protocol properties to SimpleMapAttributeDefinition
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-4454:
----------------------------------
Summary: Convert protocol properties to SimpleMapAttributeDefinition
Key: WFLY-4454
URL: https://issues.jboss.org/browse/WFLY-4454
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently we roll our own PropertyResourceDefinition child resources. We should just reuse SimpleMapAttributeDefinition.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4453) Convert cache store properties to SimpleMapAttributeDefinition
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-4453:
----------------------------------
Summary: Convert cache store properties to SimpleMapAttributeDefinition
Key: WFLY-4453
URL: https://issues.jboss.org/browse/WFLY-4453
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
We currently roll our own StorePropertyResourceDefinition child resources for cache store properties. We should reuse SimpleMapAttributeDefinition.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4452) Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-4452:
----------------------------------
Summary: Use Flag.RESTART_RESOURCE_SERVICES for child resources of cache
Key: WFLY-4452
URL: https://issues.jboss.org/browse/WFLY-4452
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Currently, the attributes for each child resource of a cache use RESTART_ALL_SERVICES, thus any change to one of these attributes requires all services to restart. This is overkill, since only the services of the parent resource (i.e. cache) actually require restarting.
Ideally, each child resource should create a runtime service for its corresponding sub-configuration. e.g. the transaction resource would create a Service<TransactionConfiguration>. Thus the cache resource's add handler becomes much less complex - and the corresponding Service<Configuration> need only depend on the sub-configuration services for each child resource.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (WFLY-4451) Security ModuleClassLoaderLocator.CombinedClassLoader does not implement getResources
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-4451:
----------------------------------
Summary: Security ModuleClassLoaderLocator.CombinedClassLoader does not implement getResources
Key: WFLY-4451
URL: https://issues.jboss.org/browse/WFLY-4451
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 9.0.0.Alpha1
Reporter: Brad Maxwell
Assignee: Brad Maxwell
org.jboss.as.security.plugins.ModuleClassLoaderLocator.CombinedClassLoader does not implement getResources. This classloader combines a module classloader with the thread context classloader. It implements loadClass, getResource & getResourceAsStream and checks the module classloader first and if it finds it returns it else checks the TCCL.
It does not implement getResources which causes custom security login modules to not be able to locate resources via getResources.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months