December 2019 - jboss-jira - Jboss List Archives

[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 updated DROOLS-4799: -------------------------------- Attachment: scesim-list.png dmn-dt-expression-constraint.png dmn-dt-enumeration-constraint.png > 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 > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12858) Eliminate redundant buffer allocation/copying when marshalling CommandDispatcher commands/responses

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12858: ----------------------------------- Summary: Eliminate redundant buffer allocation/copying when marshalling CommandDispatcher commands/responses Key: WFLY-12858 URL: https://issues.redhat.com/browse/WFLY-12858 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1399) Race condition between JCA Capacity Filler and new connections creation

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/JBJCA-1399?page=com.atlassian.jira.plugi... ] Flavia Rainone resolved JBJCA-1399. ----------------------------------- Resolution: Done > Race condition between JCA Capacity Filler and new connections creation > ----------------------------------------------------------------------- > > Key: JBJCA-1399 > URL: https://issues.redhat.com/browse/JBJCA-1399 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Critical > > JCA Capacity Filler is unaware of connections being created in a separate thread, which can lead to unexpected behavior, such as the pool being filled with too many connections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1399) Race condition between JCA Capacity Filler and new connections creation

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/JBJCA-1399?page=com.atlassian.jira.plugi... ] Flavia Rainone updated JBJCA-1399: ---------------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/695 > Race condition between JCA Capacity Filler and new connections creation > ----------------------------------------------------------------------- > > Key: JBJCA-1399 > URL: https://issues.redhat.com/browse/JBJCA-1399 > Project: IronJacamar > Issue Type: Bug > Components: Core > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Critical > > JCA Capacity Filler is unaware of connections being created in a separate thread, which can lead to unexpected behavior, such as the pool being filled with too many connections. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

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

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4799: -------------------------------------- Story Points: 1 (was: 2) > 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 > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, expression-list_error.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, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4862) Dsl mapping fails during validation in Guided Rule Editor

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-4862?page=com.atlassian.jira.plug... ] Anna Dupliak updated DROOLS-4862: --------------------------------- Steps to Reproduce: # Go to test project *Traffic* # Add DSL asset in traffic package with following content: {code} [when]There is a Person with age equals to {age}=p:Person(age == {age}) {code} # Add Guided Rule asset and add a cause {code}[when]There is a Person with age equals to {age}=p:Person(age == {age}) {code} # Change value age to 10 # Press *validate* button # Expected successfully passed validation was: # Go to test project *Traffic* # Add DSL asset in traffic package with following content: {code} [when]There is a Person with age equals to {age}=p:Person(age == {age}) {code} # Add Guided Rule asset and add a cause *"[when]There is a Person with age equals to {age}=p:Person(age == {age})"* # Change value age to 10 # Press *validate* button # Expected successfully passed validation > Dsl mapping fails during validation in Guided Rule Editor > --------------------------------------------------------- > > Key: DROOLS-4862 > URL: https://issues.redhat.com/browse/DROOLS-4862 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.31.0.Final > Reporter: Anna Dupliak > Assignee: Michael Anstis > Priority: Major > Labels: BusinessCentral > > Dsl written expressions validation fails with errors: > {code} > [KBase: kbase1]: [8] No mapping entries for expanding: There is a Person with age equals to 10 > [KBase: kbase1]: [8] Unable to expand: There is a Person with age equals to 10 > [KBase: kbase1]: [ERR 102] Line 8:8 mismatched input 'is' in rule "rule with DSL" > [KBase: defaultKieBase]: [8] No mapping entries for expanding: There is a Person with age equals to 10 > [KBase: defaultKieBase]: [8] Unable to expand: There is a Person with age equals to 10 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4862) Dsl mapping fails during validation in Guided Rule Editor

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4862: ------------------------------------ Summary: Dsl mapping fails during validation in Guided Rule Editor Key: DROOLS-4862 URL: https://issues.redhat.com/browse/DROOLS-4862 Project: Drools Issue Type: Bug Components: Guided Rule Editor Affects Versions: 7.31.0.Final Reporter: Anna Dupliak Assignee: Michael Anstis Dsl written expressions validation fails with errors: {code} [KBase: kbase1]: [8] No mapping entries for expanding: There is a Person with age equals to 10 [KBase: kbase1]: [8] Unable to expand: There is a Person with age equals to 10 [KBase: kbase1]: [ERR 102] Line 8:8 mismatched input 'is' in rule "rule with DSL" [KBase: defaultKieBase]: [8] No mapping entries for expanding: There is a Person with age equals to 10 [KBase: defaultKieBase]: [8] Unable to expand: There is a Person with age equals to 10 {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-4699?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-4699: ----------------------------- Fix Version/s: 19.0.0.Beta1 > Expose EJB3 deployment information at runtime > --------------------------------------------- > > Key: WFLY-4699 > URL: https://issues.redhat.com/browse/WFLY-4699 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Bilgehan Ozpeynirci > Assignee: Cheng Fang > Priority: Minor > Fix For: 19.0.0.Beta1 > > > User will be able to get EJB Deployment Information at runtime for the following areas: > - Class name > - Local JNDI name > - Remote JNDI name > - Security roles > - Bean statistics (beans in use, access count, idle count, ...) > - Destination JNDI (for MDBs) > - Activation config properties > - EJB timeout (Stateful Timeouts , and Stateless Instance timeout) > A lot of this information were previously (EAP 5) obtained from the deployment descriptor that was published by the bean ("deploymentDescriptor" attribute). In the past, this metadata could be retrieved from EAP 5 via jmx which no longer exists in EAP 6+ (JBoss AS 7+). Now with EJB 3, users provide that information through annotations (and also through the Deployment Descriptor file), so users need means to get those informations at runtime. > The goal of this is not only for MDB but for all kinds of EJB (session, stateful, MDB, ...) > MORE INFO: > The local and remote JNDI are related to Session EJBs. > However we need to access the JNDI of the destination configured for the MDB. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4699) Expose EJB3 deployment information at runtime

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-4699?page=com.atlassian.jira.plugin... ] Cheng Fang reassigned WFLY-4699: -------------------------------- Assignee: Cheng Fang > Expose EJB3 deployment information at runtime > --------------------------------------------- > > Key: WFLY-4699 > URL: https://issues.redhat.com/browse/WFLY-4699 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Bilgehan Ozpeynirci > Assignee: Cheng Fang > Priority: Minor > > User will be able to get EJB Deployment Information at runtime for the following areas: > - Class name > - Local JNDI name > - Remote JNDI name > - Security roles > - Bean statistics (beans in use, access count, idle count, ...) > - Destination JNDI (for MDBs) > - Activation config properties > - EJB timeout (Stateful Timeouts , and Stateless Instance timeout) > A lot of this information were previously (EAP 5) obtained from the deployment descriptor that was published by the bean ("deploymentDescriptor" attribute). In the past, this metadata could be retrieved from EAP 5 via jmx which no longer exists in EAP 6+ (JBoss AS 7+). Now with EJB 3, users provide that information through annotations (and also through the Deployment Descriptor file), so users need means to get those informations at runtime. > The goal of this is not only for MDB but for all kinds of EJB (session, stateful, MDB, ...) > MORE INFO: > The local and remote JNDI are related to Session EJBs. > However we need to access the JNDI of the destination configured for the MDB. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-82) Release Elytron Web 1.7.0.CR3

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-82?page=com.atlassian.jira.plugin... ] Farah Juma resolved ELYWEB-82. ------------------------------ Resolution: Done > Release Elytron Web 1.7.0.CR3 > ----------------------------- > > Key: ELYWEB-82 > URL: https://issues.redhat.com/browse/ELYWEB-82 > Project: Elytron Web > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.7.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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