[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-2788:
---------------------------------------
[~uxdlc] the example that [~ron-murhammer] presented is a good one. Other simple examples:
* comparing two (or more) transactions to check for frauds and/or duplications
* comparing two (or more) passengers to prioritize a flight upgrade or a rebook
* comparing two (or more) rating plans to select which one to use to rate a phone call
etc...
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache use
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ]
Scott Marlow commented on WFLY-11010:
-------------------------------------
Seems like we need an initiator per session factory, instead of per application classloader (service loader), as the WildFlyCustomRegionFactoryInitiator.resolveRegionFactory(Map configurationValues, ServiceRegistryImplementor registry) is only called once per application.
Sometimes, the ServiceContributorImpl.contribute(StandardServiceRegistryBuilder) is called more than once while debugging (with a deployment that has two persistence units) but that appears to be pure luck, as sometimes it is only called once.
> Document 2lc/JTA integration properties and add better detection of ehcache use
> -------------------------------------------------------------------------------
>
> Key: WFLY-11010
> URL: https://issues.jboss.org/browse/WFLY-11010
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 15.0.0.Alpha1
>
>
> Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration.
> Also automatically set "wildfly.jpa.regionfactory" to false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache").
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Ron Murhammer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Ron Murhammer edited comment on DROOLS-2788 at 9/18/18 2:42 PM:
----------------------------------------------------------------
The most common case is you have rules that are dealing with the checking of multiple objects and testing conditions. So imagine something like I want to find all accounts that have 2 disputes open to flag them as high risk. So I'd define an account object and then multiple dispute objects. So the test would be something like:
Given
- Account $a
- Dispute $d1: account == $a, status == open
- Dispute $d2: account == $a, status == open
Expected
- $a.isHighRisk == true
was (Author: ron-murhammer):
The most common case is you have rules that are dealing with the checking of multiple objects and testing conditions. So imagine something like I want to find all accounts that have 2 disputes open to flag them as high risk. So I'd define an account object and then multiple dispute objects. So the test would be something like:
Given
- Account $a
- Dispute $d1: account == $a, status == open
- Dispute $d2: account == $a, status == open
Expected
- $a.isHighRisk == true
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Ron Murhammer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Ron Murhammer commented on DROOLS-2788:
---------------------------------------
The most common case is you have rules that are dealing with the checking of multiple objects and testing conditions. So imagine something like I want to find all accounts that have 2 disputes open to flag them as high risk. So I'd define an account object and then multiple dispute objects. So the test would be something like:
Given
- Account $a
- Dispute $d1: account == $a, status == open
- Dispute $d2: account == $a, status == open
Expected
- $a.isHighRisk == true
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2788:
-------------------------------------
[~tirelli] I was drafting up a long winded question around this, but think it might be more efficient if I simply ask: Why would a "user I want to define multiple data/domain object instances per scenario." Or could you give me a use case scenario?
p.s. in the scenario grid we represented nested DO's using a delimited string: "applicant.Age." Is that correct [~danielezonca]
> UX to support selection of multiple data/domain object instances
> ----------------------------------------------------------------
>
> Key: DROOLS-2788
> URL: https://issues.jboss.org/browse/DROOLS-2788
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png
>
>
> As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months