August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-655) Customizable Console Log Viewer

by Pandurang Memane (Jira)

[ https://issues.jboss.org/browse/WFCORE-655?page=com.atlassian.jira.plugin... ] Pandurang Memane reopened WFCORE-655: ------------------------------------- > Customizable Console Log Viewer > ------------------------------- > > Key: WFCORE-655 > URL: https://issues.jboss.org/browse/WFCORE-655 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Carlton Zachary > Assignee: James Perkins > Priority: Optional > > Currently the Console log viewer only points to jboss.server.log.dir. In our Domain environment we have our server.log write to a non-default location. This is defined in the host-slave.xml as: > <paths> > <path name="custom.jboss.server.log.dir" path="/apps/logs/server1"/> > </paths> > it is then referenced in the domain.xml file logging subsystem as: > <file relative-to="custom.jboss.server.log.dir" path="server.log"/> > Can the Console logviewer be enhanced to allow it to be configured to point to a custom server.log location? > https://bugzilla.redhat.com/show_bug.cgi?id=1191180 > Thanks -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4258) DMN UX - overlay information about a single scenario run

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4258?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4258: -------------------------------------- Story Points: 2 (was: 3) > DMN UX - overlay information about a single scenario run > -------------------------------------------------------- > > Key: DROOLS-4258 > URL: https://issues.jboss.org/browse/DROOLS-4258 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze the execution of a *single scenario* in the DMN model > - user clicks on "a link" related to the scenario to analyze > - user lands on DMN editor with overlay information about decision executed, decision failed and for each decision the possibility see actual and expected value (from the scenario) and to open an executed decision table to see which row has been evaluated -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4481: -------------------------------------- Story Points: 5 > [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX > ------------------------------------------------------------------------------ > > Key: DROOLS-4481 > URL: https://issues.jboss.org/browse/DROOLS-4481 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 2019-08-26 17.48.30.gif, Screen Shot 2019-08-26 at 18.11.01.png > > > *Requirement* > It should be possible to generate data types from imported data models (java classes). > --- > *Current scenario* > Currently, users can create Data Objects on Business Central. See: > !2019-08-26 17.48.30.gif|width=600! > However users cannot re-use Data Objects as Data Types. > --- > *Description* > Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one: > !Screen Shot 2019-08-26 at 18.11.01.png|width=600! > --- > *Questions to clarify at requirement level* > 1) Some DOs can be quite complex and some fields can be impossible to guess. > - Person > -- name (Some strange type) > -- age (Integer) > What should we do? Import name as "Any"? Remove the name field? Or block the Person type? > 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)? -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4257) DMN UX - overlay information about an entire simulation execution

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4257?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4257: -------------------------------------- Story Points: 2 (was: 3) > DMN UX - overlay information about an entire simulation execution > ----------------------------------------------------------------- > > Key: DROOLS-4257 > URL: https://issues.jboss.org/browse/DROOLS-4257 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze coverage information of {color:red}the *whole* simulation{color} > - user clicks on "a link" near global coverage information > - user lands on DMN editor with overlay information about number of time each decision has been executed, number of time each decision succeed/fail (maybe with different colors?) -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4481: -------------------------------------- Sprint: 2019 Week 35-37 > [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX > ------------------------------------------------------------------------------ > > Key: DROOLS-4481 > URL: https://issues.jboss.org/browse/DROOLS-4481 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 2019-08-26 17.48.30.gif, Screen Shot 2019-08-26 at 18.11.01.png > > > *Requirement* > It should be possible to generate data types from imported data models (java classes). > --- > *Current scenario* > Currently, users can create Data Objects on Business Central. See: > !2019-08-26 17.48.30.gif|width=600! > However users cannot re-use Data Objects as Data Types. > --- > *Description* > Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one: > !Screen Shot 2019-08-26 at 18.11.01.png|width=600! > --- > *Questions to clarify at requirement level* > 1) Some DOs can be quite complex and some fields can be impossible to guess. > - Person > -- name (Some strange type) > -- age (Integer) > What should we do? Import name as "Any"? Remove the name field? Or block the Person type? > 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)? -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4481) [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4481?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4481: -------------------------------------- Labels: UX UXTeam drools-tools (was: drools-tools) > [DMN Designer] Data Types - Business Central Data Objects as DMN Data Types UX > ------------------------------------------------------------------------------ > > Key: DROOLS-4481 > URL: https://issues.jboss.org/browse/DROOLS-4481 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: 2019-08-26 17.48.30.gif, Screen Shot 2019-08-26 at 18.11.01.png > > > *Requirement* > It should be possible to generate data types from imported data models (java classes). > --- > *Current scenario* > Currently, users can create Data Objects on Business Central. See: > !2019-08-26 17.48.30.gif|width=600! > However users cannot re-use Data Objects as Data Types. > --- > *Description* > Data Objects (DO) are pretty similar to DMN Data Types (DT). So, would be great to import the DO above as a DMN DT like the following one: > !Screen Shot 2019-08-26 at 18.11.01.png|width=600! > --- > *Questions to clarify at requirement level* > 1) Some DOs can be quite complex and some fields can be impossible to guess. > - Person > -- name (Some strange type) > -- age (Integer) > What should we do? Import name as "Any"? Remove the name field? Or block the Person type? > 2) Do we need a specific component to import Data Objects as Data Types? Couldn't we just add Data Objects in the type dropdown, but use a different category (Default, Custom Data Types, Data Objects)? -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-3953. --------------------------------------- Resolution: Done [~karreiro] Marking as resolved per team review. cc. [~gabriolo] > DMN UX - overlay validation error reporting > ------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png > > > As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table. > I want to see this kind of errors in the decisions and at diagram level. > * As a user I want to run a validation test within the DMN editor, using the Validate toolbar action, to be able to identify elements within the graph or grids that have errors, so that I can resolve the issues. > * As a user when I save a file (and it is validated) I want to be informed if there are any validation errors, so that I'm aware that there are issues that need to be resolved. > * As a user when I test a rule in the Scenario tool and any scenarios fail due to a syntax errors within DMN, I need to be able to easily identify the portions of the DMN file with errors so that I can fix them. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4467) PMML with capitalized field names does not work

by Lance Leverich (Jira)

[ https://issues.jboss.org/browse/DROOLS-4467?page=com.atlassian.jira.plugi... ] Lance Leverich updated DROOLS-4467: ----------------------------------- Sprint: 2019 Week 35-37 > PMML with capitalized field names does not work > ----------------------------------------------- > > Key: DROOLS-4467 > URL: https://issues.jboss.org/browse/DROOLS-4467 > Project: Drools > Issue Type: Bug > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > Labels: CustomerFocus > Attachments: single_audit_dectree.xml > > > PMML files that contain field names with the first letter capitalized do not generate the proper POJOs, and consequently do not work. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4467) PMML with capitalized field names does not work

by Lance Leverich (Jira)

[ https://issues.jboss.org/browse/DROOLS-4467?page=com.atlassian.jira.plugi... ] Lance Leverich updated DROOLS-4467: ----------------------------------- Labels: CustomerFocus (was: ) > PMML with capitalized field names does not work > ----------------------------------------------- > > Key: DROOLS-4467 > URL: https://issues.jboss.org/browse/DROOLS-4467 > Project: Drools > Issue Type: Bug > Reporter: Lance Leverich > Assignee: Lance Leverich > Priority: Major > Labels: CustomerFocus > Attachments: single_audit_dectree.xml > > > PMML files that contain field names with the first letter capitalized do not generate the proper POJOs, and consequently do not work. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4630) Move to jakarta.inject:jakarta.inject-api

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4630: ------------------------------------ Summary: Move to jakarta.inject:jakarta.inject-api Key: WFCORE-4630 URL: https://issues.jboss.org/browse/WFCORE-4630 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Yeray Borges Assignee: Yeray Borges Migrate from javax.inject:javax.inject:1 to jakarta.inject:jakarta.inject-api:1.0 once it has been formally released and available at maven central. Jakarta specification release: https://github.com/jakartaee/specifications/pull/63 WildFly boms would need to be revised. WildFly feature-packs are also using the javax.inject:javax.inject dependency. Exclusions for other dependencies could be required -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 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 August 2019