[JBoss JIRA] (WFLY-13257) Improvements for MicroProfile Fault Tolerance quickstart
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13257?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13257:
----------------------------------
Description:
Follow up on WFLY-12770 – the initial implementation:
* Investigate/update OpenShift Support
* Include a test case (I have a local unfinished branch)
* Demonstrate @Bulkhead
* Demonstrate @Asynchronous
was:
Follow up on WFLY-12770 – the initial implementation:
* OpenShift Support
* Include a test case (I have a local unfinished branch)
* Demonstrate @Bulkhead
* Demonstrate @Asynchronous
> Improvements for MicroProfile Fault Tolerance quickstart
> --------------------------------------------------------
>
> Key: WFLY-13257
> URL: https://issues.redhat.com/browse/WFLY-13257
> Project: WildFly
> Issue Type: Task
> Components: MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> Follow up on WFLY-12770 – the initial implementation:
> * Investigate/update OpenShift Support
> * Include a test case (I have a local unfinished branch)
> * Demonstrate @Bulkhead
> * Demonstrate @Asynchronous
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFLY-13257) Improvements for MicroProfile Fault Tolerance quickstart
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/WFLY-13257?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated WFLY-13257:
----------------------------------
Description:
Follow up on WFLY-12770 – the initial implementation:
* OpenShift Support
* Include a test case (I have a local unfinished branch)
* Demonstrate @Bulkhead
* Demonstrate @Asynchronous
> Improvements for MicroProfile Fault Tolerance quickstart
> --------------------------------------------------------
>
> Key: WFLY-13257
> URL: https://issues.redhat.com/browse/WFLY-13257
> Project: WildFly
> Issue Type: Task
> Components: MP Fault Tolerance, Quickstarts
> Affects Versions: 19.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> Follow up on WFLY-12770 – the initial implementation:
> * OpenShift Support
> * Include a test case (I have a local unfinished branch)
> * Demonstrate @Bulkhead
> * Demonstrate @Asynchronous
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5135) Drools Setup › Exception Handling in Drools Rule Condition
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5135?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-5135.
---------------------------------
Resolution: Won't Do
Sorry, what you're asking is not doable.
> Drools Setup › Exception Handling in Drools Rule Condition
> -----------------------------------------------------------
>
> Key: DROOLS-5135
> URL: https://issues.redhat.com/browse/DROOLS-5135
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Affects Versions: 7.15.0.Final
> Reporter: Bishnu Shankar Pandey
> Assignee: Mario Fusco
> Priority: Major
>
> How can we do rule wise exception handling in the drools rule condition? My scenario is how to handle scenarios when the schema of an event changes.
> For example, let's say Initially I have an event that has 5 members namely name,num1,num2,num3,num4. I started creating rules for the event and the rule engine is running for some time. After that let's assume there is a scenario in which one of the class members (say num4) is removed from the event because of some reason. Now what I can do now is to change the Event class, but all the rules associated with that member will give me exceptions. The exceptions will also affect other rules which can run with the current data. Is there any way to handle exception in rule condition for specific rule and restrict it to disturb the independent rules.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month