June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6938) Startup error messages caused by expression where expressions are not allowed are confusing

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-6938?page=com.atlassian.jira.plugin... ] Lukas Vydra reassigned WFLY-6938: --------------------------------- Assignee: Lukas Vydra > Startup error messages caused by expression where expressions are not allowed are confusing > ------------------------------------------------------------------------------------------- > > Key: WFLY-6938 > URL: https://issues.redhat.com/browse/WFLY-6938 > Project: WildFly > Issue Type: Enhancement > Components: Server > Affects Versions: 10.1.0.CR1 > Reporter: Ondrej Chaloupka > Assignee: Lukas Vydra > Priority: Minor > > When a property expression is used at place where expression usage is not allowed then error message which is shown is quite confusing. From user point of view (especially the newcomer) it would be nice if the error message shows the real reason - usage of expression at place where is not permitted. > Maybe CLI could warn on usage of expression on place where is not allowed too. > Documentation recommends configuration with CLI, editing of XML file is common too. More of it there are some tasks which are harder to be done with CLI and editing XML is faster/easier. > Examples: > Setting > {code} > /subsystem=ee/managed-executor-service=default:write-attribute(name=context-service, value="${my.context.service}") > {code} > ends with this error message during startup > {code} > 14:13:21,076 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "ee"), > ("managed-executor-service" => "default") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.concurrent.ee.context.service.${my.context.service}"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.concurrent.ee.executor.default is missing [jboss.concurrent.ee.context.service.${my.context.service}]"]} > {code} > another confusion is setting name of host in {{host-slave.xml}} file. When set as > {code} > <host xmlns="urn:jboss:domain:4.2" host="${host.name}"> > {code} > then NullPointerException is thrown. > {code} > [Host Controller] 14:18:45,238 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) > at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188) > at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:594) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) > at java.lang.Thread.run(Thread.java:745)[Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError > at [row,col]:[3,1][Host Controller] Message: WFLYCTL0197: Unexpected attribute 'host' encountered > at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117) > at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:311) > at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79) > at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50) > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) ... 4 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5291: ------------------------------- Labels: drools-tools (was: drools-tools kogito-tooling) > Import of empty scesim file leads to Unexpected error > ----------------------------------------------------- > > Key: DROOLS-5291 > URL: https://issues.redhat.com/browse/DROOLS-5291 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Fix For: 7.40.0.Final > > Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png > > > If user generate a scesim file using vs code extention it is not comparable with BC. > Use Vscode generated files [^Traffic.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5147) [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX)

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-5147?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-5147: -------------------------------------- Labels: UXTeam drools-tools kogito-tooling (was: UXTeam drools-tools) > [DMN Designer] DMN Decision Table - Input/Output clauses enhancements (UX) > -------------------------------------------------------------------------- > > Key: DROOLS-5147 > URL: https://issues.redhat.com/browse/DROOLS-5147 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UXTeam, drools-tools, kogito-tooling > Attachments: prototype.png > > > Currently, the DMN Decision Tables input/output clauses work fine, but they have the following unpractical scenarios: > - When users have a structure input node "associated" with an input clause (input column), they frequently need to go back to the data types page and remember the name of some field. > - When users select a structure data type as the type of an output clause, they need to create sub-columns for each field manually. > The goal for this JIRA is to get input from UX to enhance interactions with input and output clauses. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5291: ------------------------------- Sprint: (was: 2020 Week 25-27 (from Jun 15)) > Import of empty scesim file leads to Unexpected error > ----------------------------------------------------- > > Key: DROOLS-5291 > URL: https://issues.redhat.com/browse/DROOLS-5291 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Fix For: 7.40.0.Final > > Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png > > > If user generate a scesim file using vs code extention it is not comparable with BC. > Use Vscode generated files [^Traffic.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5009) Request for enhancement in the JBoss EAP CLI generic type "command"

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5009?page=com.atlassian.jira.plug... ] Jean Francois Denise moved EAP7-1508 to WFCORE-5009: ---------------------------------------------------- Project: WildFly Core (was: JBoss EAP Planning for version 7 and above) Key: WFCORE-5009 (was: EAP7-1508) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: CLI (was: CLI) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) Affects Version/s: (was: 7.3.0.GA) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Request for enhancement in the JBoss EAP CLI generic type "command" > ------------------------------------------------------------------- > > Key: WFCORE-5009 > URL: https://issues.redhat.com/browse/WFCORE-5009 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Major > Labels: Previous_RFE > > One of our strategic customers, requested an enhancement in the JBoss EAP CLI. Currently they are using in their scripts the Generic type Command (https://developer.jboss.org/wiki/GenericTypeCLICommands) to set the properties of a resource. > Unfortunately that does not work in several cases. For example when they need to set attributes like the following: > /core-service=management/access=authorization:write-attribute(name=permission-combination-policy,value=permissive) > /core-service=management/access=authorization:write-attribute(name=provider,value=rbac) > This can not be done with the command syntax: > [standalone@127.0.0.1:9999 /] command add --node-type=/core-service=management/access --command-name=access > Failed to validate input: operation response doesn't contain result info. > It would be extremely helpful for us to have an improvement in the CLI that allows setting multiple attributes on resources referenced by 'command'. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5247) Implement "Transformations" logic

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5247?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5247: ------------------------------------- Story Points: 11 (was: 5) Estimated Difficulty: High (was: Medium) > Implement "Transformations" logic > --------------------------------- > > Key: DROOLS-5247 > URL: https://issues.redhat.com/browse/DROOLS-5247 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Implement the overall flow to manage the "Transformations/Local Transformations" spec (see http://dmg.org/pmml/v4-4/Transformations.html) > This first implementation will not cover all the spec, but it must be designed to be easily extended to (incrementally) cover all the use cases -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5071) Enable kie-pmml-new in drools build

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5071?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5071. ------------------------------------ Resolution: Duplicate Implemented inside DROOLS-5372 > Enable kie-pmml-new in drools build > ----------------------------------- > > Key: DROOLS-5071 > URL: https://issues.redhat.com/browse/DROOLS-5071 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5436) Rename kie-pmml-new

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5436: ---------------------------------------- Summary: Rename kie-pmml-new Key: DROOLS-5436 URL: https://issues.redhat.com/browse/DROOLS-5436 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Rename kie-pmml-new module to something more meaningful (to be decided) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5435) Create kie-pmml-new dependencies pom

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5435: ---------------------------------------- Summary: Create kie-pmml-new dependencies pom Key: DROOLS-5435 URL: https://issues.redhat.com/browse/DROOLS-5435 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Create a maven "pom" module that defines all the kie-pmml-new dependencies. Suche module should import kie-pmml-bom (for dependencyManagement) and declare all the kie-pmml-new modules. Then, client module would just need to declare such pom as dependency (with "pom" type) e.g. <dependencies> ... <dependency> <dependency> <groupId>org.kie</groupId> <artifactId>kie-pmml-dependenciesi</artifactId> <type>pom</type> </dependency> </dependency> </dependencies> -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5378) Alpha Node ordering

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5378?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5378: -------------------------------------- Release Notes Text: TODO: Affects: Documentation (Ref Guide, User Guide, etc.),Release Notes > Alpha Node ordering > ------------------- > > Key: DROOLS-5378 > URL: https://issues.redhat.com/browse/DROOLS-5378 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Re-order Alpha Node based on some strategies: > - Expression usage count > - Other strategies : Chapter 9 "Ordering Conditions" in http://i.stanford.edu/pub/cstr/reports/cs/tr/86/1124/CS-TR-86-1124.pdf > It would contribute to maximise sharing and minimise the number of evaluations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2020