November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2148) not able to execute a drl file when packaged inside a jar file

by Vardhaman Magadum (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2148?page=com.atlassian.jira.plugi... ] Vardhaman Magadum updated DROOLS-2148: -------------------------------------- Attachment: Rule1.drl > not able to execute a drl file when packaged inside a jar file > -------------------------------------------------------------- > > Key: DROOLS-2148 > URL: https://issues.jboss.org/browse/DROOLS-2148 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.2.0.Final > Reporter: Vardhaman Magadum > Assignee: Mario Fusco > Attachments: Jar Structure.png, Rule1.drl, eclipse project.png, projectStructure.png > > > Hi all, > I have created a simplest rule project in KIE workbench 7.2, After build and deploy i am able to download the jar for my project from the artifact repository. now i want to execute the rules from a java maven project. I have put the jar in the resources folder of the maven project, scanning the jar and trying to load all the rule artifacts in the kie base. but i am not able to execute the rules inside the drl file which is inside the jar file. I have attached the drl file, jar structure, eclipse project structure and debug in eclipse. please help, pls update if any further details required. > Thanks > Vardhaman -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2148) not able to execute a drl file when packaged inside a jar file

by Vardhaman Magadum (JIRA)

Vardhaman Magadum created DROOLS-2148: ----------------------------------------- Summary: not able to execute a drl file when packaged inside a jar file Key: DROOLS-2148 URL: https://issues.jboss.org/browse/DROOLS-2148 Project: Drools Issue Type: Feature Request Components: core engine Affects Versions: 7.2.0.Final Reporter: Vardhaman Magadum Assignee: Mario Fusco Hi all, I have created a simplest rule project in KIE workbench 7.2, After build and deploy i am able to download the jar for my project from the artifact repository. now i want to execute the rules from a java maven project. I have put the jar in the resources folder of the maven project, scanning the jar and trying to load all the rule artifacts in the kie base. but i am not able to execute the rules inside the drl file which is inside the jar file. I have attached the drl file, jar structure, eclipse project structure and debug in eclipse. please help, pls update if any further details required. Thanks Vardhaman -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9564) Segregate EJB client clustering tests into separate profile

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9564: ---------------------------------- Summary: Segregate EJB client clustering tests into separate profile Key: WFLY-9564 URL: https://issues.jboss.org/browse/WFLY-9564 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Because the EJB client relies heavily on static global context, the our ejb client tests need to be run with reuseForks disabled. This slows down the entire clustering testsuite significantly. Instead we should isolate the ejb client tests into a separate profile, such that the rest of the clustering testsuite can enable reuseForks. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9564) Segregate EJB client clustering tests into separate profile

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9564?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-9564: ---------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > Segregate EJB client clustering tests into separate profile > ----------------------------------------------------------- > > Key: WFLY-9564 > URL: https://issues.jboss.org/browse/WFLY-9564 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Because the EJB client relies heavily on static global context, the our ejb client tests need to be run with reuseForks disabled. This slows down the entire clustering testsuite significantly. > Instead we should isolate the ejb client tests into a separate profile, such that the rest of the clustering testsuite can enable reuseForks. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-34) Reset connection attributes when returning to pool

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-34?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-34: ---------------------------- Affects Version/s: 0.2 (was: 0,2) > Reset connection attributes when returning to pool > -------------------------------------------------- > > Key: AG-34 > URL: https://issues.jboss.org/browse/AG-34 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > > Connections that are acquired from the pool should have their attributes according to the configuration. > > This is particularly important for attributes relating to transactions (and these are the ones addressable now, as there are default values for them supplied in the configuration) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-41) Make final some classes that are not intended to be extended

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-41?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-41. ----------------------------- Resolution: Done > Make final some classes that are not intended to be extended > ------------------------------------------------------------ > > Key: AG-41 > URL: https://issues.jboss.org/browse/AG-41 > Project: Agroal > Issue Type: Enhancement > Components: pool > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-42) Update HikariCP version

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-42?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-42. ----------------------------- Resolution: Done > Update HikariCP version > ----------------------- > > Key: AG-42 > URL: https://issues.jboss.org/browse/AG-42 > Project: Agroal > Issue Type: Enhancement > Components: hikari > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-40) Misc. code improvements suggested by static analysis

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-40?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-40. ----------------------------- Resolution: Done > Misc. code improvements suggested by static analysis > ---------------------------------------------------- > > Key: AG-40 > URL: https://issues.jboss.org/browse/AG-40 > Project: Agroal > Issue Type: Enhancement > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-33) Calling close does not seem to close a connection

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-33?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-33. ----------------------------- Fix Version/s: 0.3 Resolution: Done > Calling close does not seem to close a connection > ------------------------------------------------- > > Key: AG-33 > URL: https://issues.jboss.org/browse/AG-33 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.2 > Reporter: Paulo Lopes > Assignee: Luis Barreiro > Fix For: 0.3 > > > In vert.x we have the test: > {code} > @Test > public void testStreamOnClosedConnection() { > String sql = "SELECT ID, FNAME, LNAME FROM select_table ORDER BY ID"; > final AtomicInteger cnt = new AtomicInteger(0); > final SQLConnection conn = connection(); > conn.queryStream(sql, onSuccess(res -> { > conn.close(); > res.resultSetClosedHandler(v -> { > fail("Should not happen"); > }).handler(row -> { > fail("Should not happen"); > }).endHandler(v -> { > fail("Should not happen"); > }).exceptionHandler(t -> { > testComplete(); > }); > })); > await(); > } > {code} > Now once the query is run we call conn.close() and all remaining handlers show fail except the exception handler, however the test fails and I do get the data from the result set. > This is quite strange since it works for other pools C3P0, Hikari, BoneCP. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2122) Error when drl file is opened with in project with runtime classes

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2122?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-2122: ----------------------------------- Assignee: Mario Fusco (was: Kris Verlaenen) > Error when drl file is opened with in project with runtime classes > ------------------------------------------------------------------- > > Key: DROOLS-2122 > URL: https://issues.jboss.org/browse/DROOLS-2122 > Project: Drools > Issue Type: Bug > Components: eclipse plugin > Affects Versions: 7.3.0.Final > Environment: DevstudioIS 11.1.0.Beta1 > Brms 6.4.6.GA > Reporter: Tomas David > Assignee: Mario Fusco > Priority: Blocker > Fix For: 7.5.0.Final > > Attachments: Screenshot from 2017-11-09 09-55-05.png, devstudiolog.log > > > If new drools project is created with build using Java and Drools classes, error is displayed after drl file is opened. > This blocks also other functions like add a breakpoint or show content assist menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 November 2017