August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10518) Connection to remote Artemis broker must not require the presence of a local Artemis broker

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-10518?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFLY-10518: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > Connection to remote Artemis broker must not require the presence of a local Artemis broker > ------------------------------------------------------------------------------------------- > > Key: WFLY-10518 > URL: https://issues.jboss.org/browse/WFLY-10518 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: ehsavoie Hugonnet > > Connections to remote Artemis-based broker (including A-MQ 7) are handled in WildFly by the pooled-connection-factory resource that is in the messaging-activemq subsystem: https://wildscribe.github.io/WildFly/13.0/subsystem/messaging-activemq/se... > This pooled-connection-factory resource can be used to connect to the local Artemis server that "owns" it or to a remote Artemis broker. > However, this pooled-connection-factory always require the presence of a local Artemis server even when it connects only to a remote Artemis broker. > This use case will become more prevalent as EAP CD is used to connect to A-MQ 7 and will not embed a local Artemis server. > The presence of a local Artemis server has impact on the memory and CPU footprint of EAP on OpenShift. > This RFE will improve WildFly and EAP so that a connection with remote Artemis-based broker will no longer require the presence of a local instance of Artemis. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2787: ---------------------------------------- [~uxdlc] "Basically... within the canvas view the user action/goal is to Select a data type. And... within the Dialog view the user action/goal is to Manage (create, edit, remove) data types. Is that true?" Yes, this would indeed be my understanding of what we want to achieve. > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-362) Add Istio Services Details Automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-362?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan commented on SWSQE-362: -------------------------------------- PR sent https://github.com/Kiali-QE/kiali-qe-python/pull/64 > Add Istio Services Details Automation tests > ------------------------------------------- > > Key: SWSQE-362 > URL: https://issues.jboss.org/browse/SWSQE-362 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2792: -------------------------------- Attachment: Screen Shot 2018-08-01 at 10.11.48 AM.png > [DMN Designer] Data-types: Grid: LiteralExpression > -------------------------------------------------- > > Key: DROOLS-2792 > URL: https://issues.jboss.org/browse/DROOLS-2792 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png > > > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2792: -------------------------------- Attachment: Screen Shot 2018-08-01 at 10.20.35 AM.png > [DMN Designer] Data-types: Grid: LiteralExpression > -------------------------------------------------- > > Key: DROOLS-2792 > URL: https://issues.jboss.org/browse/DROOLS-2792 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png > > > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2792) [DMN Designer] Data-types: Grid: LiteralExpression

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2792?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2792: ------------------------------------- [~manstis] some questions: * For ContextEntry (or others), does the type need to literally be in another row or could it be wrapped below as you have in the pop-up but placed within the same row as the Name? * For all, is there some reason that the selected item is in a separate dropdown list and not within the type ahead input field. As illustrated: !Screen Shot 2018-08-01 at 10.11.48 AM.png|thumbnail! vs !Screen Shot 2018-08-01 at 10.20.35 AM.png|thumbnail! > [DMN Designer] Data-types: Grid: LiteralExpression > -------------------------------------------------- > > Key: DROOLS-2792 > URL: https://issues.jboss.org/browse/DROOLS-2792 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Attachments: DROOLS-2792.odt, Screen Shot 2018-08-01 at 10.11.48 AM.png, Screen Shot 2018-08-01 at 10.20.35 AM.png > > > *_Literal Expression_* > - (x) Grid header _could_ show Output Data Type > - (/) Editing Output Data Type is possible via Properties panel > - (x) Update header when Output Data Type is changed via Properties panel -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos commented on WFLY-10150: ------------------------------------------------ Another configuration overcome of this issue (when there are larger than expected bursts of requests and the max threads are not set to a suitable value) could be using invocation-timeout param in jboss-ejb-client.xml. If a large enough value is set then there could be no expiration. In case of expiration the request is repeated. > EJB race condition can cause client to be in awaitResponse while server is done > ------------------------------------------------------------------------------- > > Key: WFLY-10150 > URL: https://issues.jboss.org/browse/WFLY-10150 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Lin Gao > Labels: downstream_dependency > > With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2787: ------------------------------------- [~manstis] My understanding matches your explanation, I believe, but in other terms: * Property panel DT dropdown: When applied to a selected node in the canvas, the property panel dropdown would be the DT selection mechanism. Potentially, that might be the only function of the dropdown (in that context) to select a DT to apply to the node. * DT dropdown used in dialog: As part of the data type Creation or Edit action, a dropdown (or type-ahead input) would be used to select the DT and respective attributes... Basically I'd like clarity within the canvas view, the user action/goal is to Select a data type. And as you say within the Dialog view, the user action/goal is to Manage (create, edit, remove) data types. Is that true? cc [~tirelli] [~karreiro] > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-77) smallrye-config: Converter Priority is not upheld

by Michal Jurc (JIRA)

Michal Jurc created WFWIP-77: -------------------------------- Summary: smallrye-config: Converter Priority is not upheld Key: WFWIP-77 URL: https://issues.jboss.org/browse/WFWIP-77 Project: WildFly WIP Issue Type: Bug Components: MP Config Reporter: Michal Jurc Assignee: Jeff Mesnil Priority: Critical Consider a scenario with two {{Coverter}} services available in service loader: {code}@Priority(101) public class Return101Converter implements Converter<Integer> { @Override public Integer convert(String value) { return 101; } } {code} {code}@Priority(102) public class Return102Converter implements Converter<Integer> { @Override public Integer convert(String value) { return 102; } } {code} The {{@Priority}} of the {{Converter}} services is not considered, instead, their order in provider configuration file is - the first implementation will always be preferred. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-77) smallrye-config: Converter Priority is not upheld

by Michal Jurc (JIRA)

[ https://issues.jboss.org/browse/WFWIP-77?page=com.atlassian.jira.plugin.s... ] Michal Jurc updated WFWIP-77: ----------------------------- Priority: Blocker (was: Critical) > smallrye-config: Converter Priority is not upheld > ------------------------------------------------- > > Key: WFWIP-77 > URL: https://issues.jboss.org/browse/WFWIP-77 > Project: WildFly WIP > Issue Type: Bug > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > Priority: Blocker > > Consider a scenario with two {{Coverter}} services available in service loader: > {code}@Priority(101) > public class Return101Converter implements Converter<Integer> { > @Override > public Integer convert(String value) { > return 101; > } > } > {code} > {code}@Priority(102) > public class Return102Converter implements Converter<Integer> { > @Override > public Integer convert(String value) { > return 102; > } > } > {code} > The {{@Priority}} of the {{Converter}} services is not considered, instead, their order in provider configuration file is - the first implementation will always be preferred. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018