December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4696) [DMN Designer] BC DOs as DMN DTs - Show a warning message into the import dialog

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4696?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4696: -------------------------------- Attachment: nested-types.webm > [DMN Designer] BC DOs as DMN DTs - Show a warning message into the import dialog > -------------------------------------------------------------------------------- > > Key: DROOLS-4696 > URL: https://issues.redhat.com/browse/DROOLS-4696 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: nested-types.webm, warning.png > > > Show a warning message into the import dialog when any Data Object name matches with some Data Type name: -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4340) Contains can not be used for String with the Expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4340?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4340: -------------------------------- Tester: Jozef Marko Affects Version/s: 7.31.0.Final (was: 7.32.0.Final) > Contains can not be used for String with the Expression editor > -------------------------------------------------------------- > > Key: DROOLS-4340 > URL: https://issues.redhat.com/browse/DROOLS-4340 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools > > Use the expression editor and check for example person.name.contains("ABC"). > Save, close the editor and reopen. "contains("ABC")" does not show up in the editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4340) Contains can not be used for String with the Expression editor

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4340?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4340: -------------------------------- Affects Version/s: 7.32.0.Final > Contains can not be used for String with the Expression editor > -------------------------------------------------------------- > > Key: DROOLS-4340 > URL: https://issues.redhat.com/browse/DROOLS-4340 > Project: Drools > Issue Type: Bug > Affects Versions: 7.31.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools > > Use the expression editor and check for example person.name.contains("ABC"). > Save, close the editor and reopen. "contains("ABC")" does not show up in the editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4799) Adding "expression" type handling for Collection type propereties

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4799: ------------------------------------- [~uxdlc] Hello, thank you for your comment. I agree with first two points. I think I am different opinion about "We don't try to convert values from expression to form-based.", because we do (try to do) conversion in DMN constraints. However it may me difficult to implement it. If [~yamer] say it is too big task, then I am fine with your proposal. > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.redhat.com/browse/DROOLS-4799 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png, expression-list_error.png, scesim-list.png > > > I need a clarification regarding the behaviour of the updated Collection Editor, in particular for this section -->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330. > Considering the editor introduces a new way to handle a Collection ("Define List"), can you please give us detailed behaviour for the following case: > - What happen if a user starts to input data inside a section (Define List/Create List) and then switch on the other one? > eg. if I start to define a List using "Define List" option (i.e. an expression) and then I change to "Create List" case. What should happen? > - Currently, after adding a Collection, the Grid cell will show "List (1)". It should be the same for "Define list" (i.e. Expression) case? > In case of additional clarificaiton, I'll update this ticket. > Hope it's clear, if not you can contact me anytime. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-287) MP Fault Tolerance - Hystrix is initialized by random module from EAR

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFWIP-287?page=com.atlassian.jira.plugin... ] Radoslav Husar closed WFWIP-287. -------------------------------- Resolution: Rejected Rejecting this, as {{initialize-in-order}} deals with EE component initialization sequencing and has nothing to do with deployment order where MP Config properties are applied. So, this is not a valid way to ensure a certain configuration. > MP Fault Tolerance - Hystrix is initialized by random module from EAR > ---------------------------------------------------------------------- > > Key: WFWIP-287 > URL: https://issues.redhat.com/browse/WFWIP-287 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Miroslav Novak > Assignee: Radoslav Husar > Priority: Critical > > If EAR container 2 MP FT modules where each has different configuration for Hystrix then it is initialized by randomly and does not respect module deployment order defined in {{META-INF/application.xml}}: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" > version="6"> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>first-module.war</web-uri> > <context-root>first-module</context-root> > </web> > </module> > <module> > <web> > <web-uri>second-module.war</web-uri> > <context-root>second-module</context-root> > </web> > </module> > </application> > {code} > It's expected that first-module would configured Hystric based on above application.xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1221) Add fail-safe and scalability functionality to the Drools (CEP) rules engine

by Tom Pijl (Jira)

[ https://issues.redhat.com/browse/DROOLS-1221?page=com.atlassian.jira.plug... ] Tom Pijl closed DROOLS-1221. ---------------------------- > Add fail-safe and scalability functionality to the Drools (CEP) rules engine > ---------------------------------------------------------------------------- > > Key: DROOLS-1221 > URL: https://issues.redhat.com/browse/DROOLS-1221 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.4.0.Final > Environment: Drools (CEP) Rule engine 6.4.0.Final > Reporter: Tom Pijl > Assignee: Mario Fusco > Priority: Major > > The Drools Rule engine is currently not fail-safe and scalable which is a requirement for Cloud deployment. > Add a possibility to persist the state of the working memory after each state change (perhaps linked to the fireAllRules()?) and related to that the possibility to restore the state in case of a crash (fail-safe requirement). > This persistent state store can also be used to synchronize multiple engine instances (scalability requirement). > Of course this has major impact on the performance of the engine, but it is the only way to make the engine useful in a multi-tenant Cloud environment -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12888: ------------------------------------ Summary: Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 (was: Upgrade jakarta.el from 3.0.3 to 3.0.4) > Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 > ------------------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Ilia Vassilev > Assignee: Ricardo Martin Camarero > Priority: Major > > https://github.com/jboss/uel/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-12888: ----------------------------------------- [~ivassile] This will be a 3.0.3.jbossorg-1 as the eclipse-ee4j controls the main release series. > Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 > ------------------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Ilia Vassilev > Assignee: Ricardo Martin Camarero > Priority: Major > > https://github.com/jboss/uel/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12888: ------------------------------------ Description: (was: https://github.com/jboss/uel/) > Upgrade jakarta.el from 3.0.3 to 3.0.3.jbossorg-1 > ------------------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Affects Versions: 18.0.1.Final > Reporter: Ilia Vassilev > Assignee: Ricardo Martin Camarero > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12888) Upgrade jakarta.el from 3.0.3 to 3.0.4

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12888?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved JBEAP-18347 to WFLY-12888: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12888 (was: JBEAP-18347) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Affects Version/s: (was: 7.2.0.GA) Fix Version/s: (was: 7.3.1.GA) > Upgrade jakarta.el from 3.0.3 to 3.0.4 > -------------------------------------- > > Key: WFLY-12888 > URL: https://issues.redhat.com/browse/WFLY-12888 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ricardo Martin Camarero > Priority: Major > > https://github.com/jboss/uel/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 December 2019