January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3523) kbase 'packages' in kmodule.xml works differently with executable-model

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-3523: ----------------------------------------- Summary: kbase 'packages' in kmodule.xml works differently with executable-model Key: DROOLS-3523 URL: https://issues.jboss.org/browse/DROOLS-3523 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.16.0.Final Reporter: Toshiya Kobayashi Assignee: Luca Molteni Attachments: execution-model-test-kbase-package.zip When we configure 'packages' attribute in kbase element in kmodule.xml, normal build works but executable-model build results in empty kbase. {code:xml} <?xml version="1.0" encoding="UTF-8"?> <kmodule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jboss.org/kie/6.0.0/kmodule"> <kbase name="mykbase" packages="rules" default="true"> <ksession name="myksession" default="true" /> </kbase> </kmodule> {code} executable-model seems to expect that the kbase's packages value must match the "package" declaration in DRL. Please confirm the behaviour with the attached execution-model-test-kbase-package.zip. * Normal build ** mvn clean install -DskipTests ** mvn clean test {noformat} ... kiePackages = [[Package name=rules], [Package name=com.sample]] Hello, john ... {noformat} * executable-model build ** mvn clean install -DgenerateModel=YES -DskipTests ** mvn clean test {noformat} ... kiePackages = [] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.341 s <<< FAILURE! - in com.example.DroolsTest ... {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3523) kbase 'packages' in kmodule.xml works differently with executable-model

by Toshiya Kobayashi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3523?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi commented on DROOLS-3523: ------------------------------------------- I'm not 100% if this is a bug. But filed this as it works differently between normal build and executable-model build. Sorry that not providing a unit test. I can explain better with the attached maven project. > kbase 'packages' in kmodule.xml works differently with executable-model > ----------------------------------------------------------------------- > > Key: DROOLS-3523 > URL: https://issues.jboss.org/browse/DROOLS-3523 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.16.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: support > Attachments: execution-model-test-kbase-package.zip > > > When we configure 'packages' attribute in kbase element in kmodule.xml, normal build works but executable-model build results in empty kbase. > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <kmodule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://jboss.org/kie/6.0.0/kmodule"> > <kbase name="mykbase" packages="rules" default="true"> > <ksession name="myksession" default="true" /> > </kbase> > </kmodule> > {code} > executable-model seems to expect that the kbase's packages value must match the "package" declaration in DRL. > Please confirm the behaviour with the attached execution-model-test-kbase-package.zip. > * Normal build > ** mvn clean install -DskipTests > ** mvn clean test > {noformat} > ... > kiePackages = [[Package name=rules], [Package name=com.sample]] > Hello, john > ... > {noformat} > * executable-model build > ** mvn clean install -DgenerateModel=YES -DskipTests > ** mvn clean test > {noformat} > ... > kiePackages = [] > [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.341 s <<< FAILURE! - in com.example.DroolsTest > ... > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11593) Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11593?page=com.atlassian.jira.plugin... ] Jan Stourac updated WFLY-11593: ------------------------------- Description: There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: {quote} Should integrated JASPI be used or allow AsHoc identity creation. {quote} proposed change: {quote} Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. {quote} And [here is full attribute description|https://github.com/wildfly/wildfly/blob/7172799ce7bda7f82b944...] in related XSD file. was: There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: {quote} Should integrated JASPI be used or allow AsHoc identity creation. {quote} proposed change: {quote} Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. {quote} > Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element > ------------------------------------------------------------------------------------------- > > Key: WFLY-11593 > URL: https://issues.jboss.org/browse/WFLY-11593 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 15.0.0.Final, 15.0.1.Final > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Minor > > There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: > {quote} > Should integrated JASPI be used or allow AsHoc identity creation. > {quote} > proposed change: > {quote} > Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. > {quote} > And [here is full attribute description|https://github.com/wildfly/wildfly/blob/7172799ce7bda7f82b944...] in related XSD file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11593) Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element

by Jan Stourac (Jira)

Jan Stourac created WFLY-11593: ---------------------------------- Summary: Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element Key: WFLY-11593 URL: https://issues.jboss.org/browse/WFLY-11593 Project: WildFly Issue Type: Bug Components: Security, Web (Undertow) Affects Versions: 15.0.1.Final, 15.0.0.Final Reporter: Jan Stourac Assignee: Darran Lofthouse There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: {quote} Should integrated JASPI be used or allow AsHoc identity creation. {quote} proposed change: {quote} Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11592) Legacy builds - Missing microprofile-config-smallrye subsystem in some configuration files

by Yeray Borges (Jira)

Yeray Borges created WFLY-11592: ----------------------------------- Summary: Legacy builds - Missing microprofile-config-smallrye subsystem in some configuration files Key: WFLY-11592 URL: https://issues.jboss.org/browse/WFLY-11592 Project: WildFly Issue Type: Bug Components: Build System Reporter: Yeray Borges Assignee: Yeray Borges Legacy builds can be activated using the following system properties: -DlegacyBuild -DlegacyRelease -Drelease microprofile-config-smallrye is not included in some server configuration files for the legacy builds. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11593) Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFLY-11593?page=com.atlassian.jira.plugin... ] Jan Stourac reassigned WFLY-11593: ---------------------------------- Assignee: Jan Stourac (was: Darran Lofthouse) > Typo and ambiguity in 'integrated-jaspi' attribute of 'application-security-domain' element > ------------------------------------------------------------------------------------------- > > Key: WFLY-11593 > URL: https://issues.jboss.org/browse/WFLY-11593 > Project: WildFly > Issue Type: Bug > Components: Security, Web (Undertow) > Affects Versions: 15.0.0.Final, 15.0.1.Final > Reporter: Jan Stourac > Assignee: Jan Stourac > Priority: Minor > > There is a typo and a little bit of ambiguity in the current description of the '{{/subsystem=undertow/application-security-domain=foo\[integrated-jaspi\]}}' attribute: > {quote} > Should integrated JASPI be used or allow AsHoc identity creation. > {quote} > proposed change: > {quote} > Whether integrated JASPI should be used. If this is disabled, ad hoc identity will be created instead. > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3512) [DMN Designer] Increase maximal size of diagram nodes, and include text wrapping.

by Thomas Mantegazzi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3512?page=com.atlassian.jira.plugi... ] Thomas Mantegazzi commented on DROOLS-3512: ------------------------------------------- [~dadossan] I think it's enough. Thank you. > [DMN Designer] Increase maximal size of diagram nodes, and include text wrapping. > --------------------------------------------------------------------------------- > > Key: DROOLS-3512 > URL: https://issues.jboss.org/browse/DROOLS-3512 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Thomas Mantegazzi > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: image-2019-01-14-09-07-56-069.png, screenshot-1.png > > > If a decision name becomes too long the name will overflow the Decision diagram. > !image-2019-01-14-09-07-56-069.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3492: -------------------------------------- [~zhutaojiajia], I like the proposal too; very well done! The only thing that is confusing to me is the third added icon called *Test Report*, when we already have it (the second one from the top, also called Test Report). Why was the new icon added? Will there be a difference between the two? If so, can't both be merged into one? If not, can they at least be neighbors? !test-report-icon.png|thumbnail! > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3492: --------------------------------- Attachment: test-report-icon.png > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11591) servlet-feature-pack-licenses.xml - remove org.glassfish:javax.json and javax.json:javax.json-api licences

by Yeray Borges (Jira)

Yeray Borges created WFLY-11591: ----------------------------------- Summary: servlet-feature-pack-licenses.xml - remove org.glassfish:javax.json and javax.json:javax.json-api licences Key: WFLY-11591 URL: https://issues.jboss.org/browse/WFLY-11591 Project: WildFly Issue Type: Task Components: Build System Affects Versions: 15.0.1.Final Reporter: Yeray Borges Assignee: Yeray Borges These dependencies are not audited in the servlet-feature-pack-licenses.xml files, instead they can be found in core-feature-pack-licenses.xml which is generated by wildfly-core. That means we can remove them from servlet-feature-pack-licenses.xml. This issue will facilitate the creation of product branches from the community ones. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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