[JBoss JIRA] (DROOLS-2438) Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule
by Rahul Vanimisetty (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2438?page=com.atlassian.jira.plugi... ]
Rahul Vanimisetty updated DROOLS-2438:
--------------------------------------
Issue Type: Bug (was: Enhancement)
> Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule
> -------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2438
> URL: https://issues.jboss.org/browse/DROOLS-2438
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.6.0.Final
> Reporter: Rahul Vanimisetty
> Assignee: Mario Fusco
> Priority: Blocker
> Labels: task
>
> In a drool template, if i am loading rules from a database, then as per my understanding each row in the database table represents a rule. So a drool template will generate a drl file in the following way :
> rule 1
> when
> condition(first row of db)
> action
> rule 2
> condition(2cd row of db)
> then
> action
> etc.
> My requirement is to have a dynamic drl generated in the following way :
> rule 1
> when
> condition 1(1st row of db)
> condition 2 (2cd row of db)
> condition 3 (3rd row of db)
> etc
> then
> action
> end
> Please suggest a way to do this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10157?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10157:
-----------------------------------------
This is an RFE and involves a big change in how the server is built.
The WildFly build brings in the core feature pack as a whole, including its dependencies, it does not rebuild it. WFLY-9911 was not about changing that. It simply changed the location where the dependencies the full build directly controls are declared.
> version of the modules defined in wildfly core cannot be overrided in wildfly full build
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-10157
> URL: https://issues.jboss.org/browse/WFLY-10157
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc)
> latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219)
> Reporter: Lin Gao
>
> I suppose it is a bug but not for sure.
> After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too.
> Like:
> {code:java}
> mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final
> {code}
> should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build
by Lin Gao (JIRA)
Lin Gao created WFLY-10157:
------------------------------
Summary: version of the modules defined in wildfly core cannot be overrided in wildfly full build
Key: WFLY-10157
URL: https://issues.jboss.org/browse/WFLY-10157
Project: WildFly
Issue Type: Bug
Components: Build System
Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc)
latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219)
Reporter: Lin Gao
Assignee: Paul Gier
I suppose it is a bug but not for sure.
After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too.
Like:
{code:java}
mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final
{code}
should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFLY-10157) version of the modules defined in wildfly core cannot be overrided in wildfly full build
by Lin Gao (JIRA)
[ https://issues.jboss.org/browse/WFLY-10157?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned WFLY-10157:
------------------------------
Assignee: (was: Paul Gier)
> version of the modules defined in wildfly core cannot be overrided in wildfly full build
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-10157
> URL: https://issues.jboss.org/browse/WFLY-10157
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Environment: latest WildFly master (commit id: 0565fe6a47a121f5d25e4810572a2d6f277420bc)
> latest WildFly core master (commit id: 2cb7088250ddad42999702841c5d3f224f185219)
> Reporter: Lin Gao
>
> I suppose it is a bug but not for sure.
> After WFLY-9911 is resolved, I think we are able to override version of modules defined in wildfly-core at maven build time too.
> Like:
> {code:java}
> mvn clean install -Dversion.org.wildfly.core=5.0.0.Alpha3-SNAPSHOT -Dversion.io.undertow=2.0.2.Final
> {code}
> should produce module: io.undertow.core:2.0.2.Final instead of io.undertow.core:2.0.3.Final which is defined in the wildfly-core.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months