April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5148) [DMN Designer] Copy/Paste is not working

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5148?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5148: -------------------------------- Component/s: DMN Editor > [DMN Designer] Copy/Paste is not working > ---------------------------------------- > > Key: DROOLS-5148 > URL: https://issues.redhat.com/browse/DROOLS-5148 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.36.0.Final > Reporter: Guilherme Gomes > Assignee: Valentino Pellegrino > Priority: Major > Labels: drools-tools > Attachments: demo.gif > > > Ctrl + C / Ctrl + V is not working on DMN editor. When users try to copy and paste a node, the name and the boxed expression are not copied: > !demo.gif|width=600! > h5. Acceptance criteria > The copy/paste feature must work for text annotations, BKMs, decisions, Inputs, knowledge sources, and decision services. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5219) [DMN Designer] Multiple output columns in decision table

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5219: ----------------------------------- Summary: [DMN Designer] Multiple output columns in decision table Key: DROOLS-5219 URL: https://issues.redhat.com/browse/DROOLS-5219 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.36.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes Attachments: multicolumn-decision-table.webm The issue is when user tries to create a decision table expression with multiple output columns. To achieve this user needs to invoke context menu with items 'Insert left / Insert right'. User has two options. He can invoke such menu from 'data' cell and 'header' cell. For data cells the feature works fine, however for header cells the operation fails and an error is shown. For more details see the video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5218) [DMN Designer] insert row menu invocation

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5218: ----------------------------------- Summary: [DMN Designer] insert row menu invocation Key: DROOLS-5218 URL: https://issues.redhat.com/browse/DROOLS-5218 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.36.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes Attachments: context-entry.webm The issue affects Firefox. On Chrome seems working fine. The issue is if user wants to invoke context menu for adding entry into context by 'Ctrl+Space' keyboard shortcut. In such a case the menu is disappearing immediately after keys are pressed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12088) JAR does not supported for deployment-overlays mechanism

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12088?page=com.atlassian.jira.plugi... ] Bartosz Baranowski resolved WFLY-12088. --------------------------------------- Resolution: Out of Date > JAR does not supported for deployment-overlays mechanism > -------------------------------------------------------- > > Key: WFLY-12088 > URL: https://issues.redhat.com/browse/WFLY-12088 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 16.0.0.Final > Reporter: Vlad Filipp > Assignee: Bartosz Baranowski > Priority: Minor > > When trying to make a link from an overlay to a JAR, classes from overlay libraries are not loaded for a linked JAR. > The situation is similar when creating a link to a JAR which is located inside EAR. > Should overlay deployment mechanism be supported for JARs? > Example standalone.xml: > {code:java} > <deployment-overlays> > ... > <deployment-overlay name="my-overlay-n1"> > <content ...> > <deployment name="my-jar-inside-ear-use-overlays-libs.jar"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12681) Provide a 'microprofile' Galleon layer

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-12681?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-12681: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12948 (was: https://github.com/wildfly/wildfly/pull/12948, https://github.com/wildfly/wildfly/pull/13023) > Provide a 'microprofile' Galleon layer > -------------------------------------- > > Key: WFLY-12681 > URL: https://issues.redhat.com/browse/WFLY-12681 > Project: WildFly > Issue Type: Feature Request > Components: Build System, MP Config, MP Fault Tolerance, MP Health, MP JWT, MP Metrics, MP OpenAPI, MP OpenTracing > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Labels: Microprofile > > We used to have a 'microprofile' layer spec aggregating all MP specs which at the moment only contained config, health and metrics which got renamed to 'observability' by WFLY-11774. > With the introduction of new specs fault tolerance, openapi, etc. we should reintroduce the 'microprofile' layer spec which contains all of the MP specs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13333) Openapi endpoint returns empty file if schema definition contains non ASCII character

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13333?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13333: ------------------------------------ Fix Version/s: 19.0.1.Final > Openapi endpoint returns empty file if schema definition contains non ASCII character > ------------------------------------------------------------------------------------- > > Key: WFLY-13333 > URL: https://issues.redhat.com/browse/WFLY-13333 > Project: WildFly > Issue Type: Bug > Components: MP OpenAPI > Affects Versions: 19.0.0.Final > Reporter: Márk Petrényi > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > Currently the {{/openapi}} endpoint returns empty file if the OpenAPI schema definition contains non ASCII characters (ie. accented letters like á,í...). > I extended the openapi quickstart for demonstration: https://github.com/petrenyi-mark/quickstart/commit/44096980ff36ff2655859f... > It seems like it is related to the content-length, since in {{OpenAPIHttpHandler}} the content-length header is set by {{String.length()}} (line 125). However before the response is actually returned, undertow validates that the actual content-length based on ByteBuffer size is not greater then the one declared in the response header. Since non ASCII characters are usually represented by 2 bytes undertow will fail, thus no content will be returned. > In {{OpenAPIHttpHandler}} setting {{string.getBytes(charset).length}} as Conetnt-Length instead of {{String.length()}} would likely resolve this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13308) wildfly-ejb-client-bom version incorrectly managed by wildfly parent

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13308?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13308: ------------------------------------ Fix Version/s: 19.0.1.Final > wildfly-ejb-client-bom version incorrectly managed by wildfly parent > -------------------------------------------------------------------- > > Key: WFLY-13308 > URL: https://issues.redhat.com/browse/WFLY-13308 > Project: WildFly > Issue Type: Bug > Components: Build System > Environment: Patched Galleon to obey dependency management (issue forthcoming) > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > Fix For: 19.0.1.Final, 20.0.0.Beta1 > > > {{wildfly-ejb-client-bom}} is defined as having version {{${ee.maven.version}}}, but the main codebase does not produce this artifact. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13338) Add the ability to pass custom predicates to the LoggingUtil log scanning methods

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13338: --------------------------------------- Summary: Add the ability to pass custom predicates to the LoggingUtil log scanning methods Key: WFLY-13338 URL: https://issues.redhat.com/browse/WFLY-13338 Project: WildFly Issue Type: Enhancement Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry LoggingUtil includes a couple methods for scanning log content looking for a particular string. Add a varargs Predicate<String> parameter to allow further analysis of a line that contains the primary string. Doing this kind of thing was useful in a test associated with JBEAP-19148. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Guilherme Gomes commented on DROOLS-4746: ----------------------------------------- [~uxdlc], any type of boxed expression :) > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4746) UX for DMN "quick test" tool

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4746?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4746: ------------------------------------------- [~karreiro] [~danielezonca] or [~tirelli] - this can be run against any type of boxed logic expression, or only Decision tables? > UX for DMN "quick test" tool > ---------------------------- > > Key: DROOLS-4746 > URL: https://issues.redhat.com/browse/DROOLS-4746 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > As a DMN author, I'd like to probe the DMN model during the authoring phase without leaving the DMN Editor. Actually, it's really important to explore the DMN model to understand with values are required by the test. > When the user run the test he can get back the results of the DMN execution. > Moreover, it would be handy to add those input/output to an existing (or new) test scenario. > *Acceptance criteria* > Users are able to: > * Execute a single node boxed expression by providing node inputs (within the DMN editor.) > * Explore the DMN model and provide inputs necessary to run a scenario test. > * Obtain results (Expected) within the DMN editor once the test is run. > Notes: > * Try to dissociate this feature from the "test scenario" concept and think of this more as a partial execution. When we're thinking about the concept of a "test scenario", we think about input values and expected outputs... however, in this new component, users will be able to provide inputs and just check the current output. > * Out of scope: Saving or exporting the "quick test." -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020