November 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4755) Need a more clear way to use RestWorkItemHandler to POST to an external service that uses application/x-www-form-urlencoded content-type

by Jonathan Fisher (Jira)

[ https://issues.jboss.org/browse/DROOLS-4755?page=com.atlassian.jira.plugi... ] Jonathan Fisher commented on DROOLS-4755: ----------------------------------------- I'll take a crack at a patch. What I'm think is look at the fields on the data object. We could probably look at the `XmlElement` to get a field name, and ignore and fields with `XmlTransient`, or even maybe have a FormEncodedParam annotation. Is there a specific libary jbpm/drools uses to examine annotations? If I created an annotation, is there an existing "Api project" I could add the annotation to? > Need a more clear way to use RestWorkItemHandler to POST to an external service that uses application/x-www-form-urlencoded content-type > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4755 > URL: https://issues.jboss.org/browse/DROOLS-4755 > Project: Drools > Issue Type: Bug > Reporter: Danny Rucker > Assignee: Mario Fusco > Priority: Minor > > Need a more clear way to POST to application/x-www-form-urlencoded endpoint. > By passing an object that contains the data needed for the endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4755) Need a more clear way to use RestWorkItemHandler to POST to an external service that uses application/x-www-form-urlencoded content-type

by Danny Rucker (Jira)

Danny Rucker created DROOLS-4755: ------------------------------------ Summary: Need a more clear way to use RestWorkItemHandler to POST to an external service that uses application/x-www-form-urlencoded content-type Key: DROOLS-4755 URL: https://issues.jboss.org/browse/DROOLS-4755 Project: Drools Issue Type: Bug Reporter: Danny Rucker Assignee: Mario Fusco Need a more clear way to POST to application/x-www-form-urlencoded endpoint. By passing an object that contains the data needed for the endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12787) Add documentation describing how to add custom HTTP headers to the management endpoints

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12787: --------------------------------------- Summary: Add documentation describing how to add custom HTTP headers to the management endpoints Key: WFLY-12787 URL: https://issues.jboss.org/browse/WFLY-12787 Project: WildFly Issue Type: Task Components: Documentation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4750) DrlParser fails to parse str[endsWith] operator

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4750?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-4750: ------------------------------------- Sorry but I'm not understanding in which version it works and in which one it doesn't. If it is working with one of the most recent of drools, then yes we close this ticket. > DrlParser fails to parse str[endsWith] operator > ----------------------------------------------- > > Key: DROOLS-4750 > URL: https://issues.jboss.org/browse/DROOLS-4750 > Project: Drools > Issue Type: Bug > Reporter: Alberto Fanjul Alonso > Assignee: Mario Fusco > Priority: Major > Attachments: str-with-reproducer.tar > > > In documentation > https://docs.jboss.org/drools/release/7.23.0.Final/drools-docs/html_singl... > operator str[endsWith] is supposed to be supported, it it is not working. > Fails with: > {code:java} > java.lang.Exception: Rule contains errors![[5,19]: [ERR 102] Line 5:19 mismatched input 'str' in rule "pnr first name end with"] > at com.amadeus.mdw.bzr.drools_reproducer.StrWithFailOnFirstCompilationErrorReproducerTest.parse(StrWithFailOnFirstCompilationErrorReproducerTest.java:58) > at com.amadeus.mdw.bzr.drools_reproducer.StrWithFailOnFirstCompilationErrorReproducerTest._03_parseStrWith(StrWithFailOnFirstCompilationErrorReproducerTest.java:74) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2399) Problem with loading resources from the bundle root (/) in OSGI environment

by Orlin Stalyanov (Jira)

[ https://issues.jboss.org/browse/JGRP-2399?page=com.atlassian.jira.plugin.... ] Orlin Stalyanov commented on JGRP-2399: --------------------------------------- [~belaban] I have added a pull request for the 3.6 branch here (https://github.com/belaban/JGroups/pull/446/files) > Problem with loading resources from the bundle root (/) in OSGI environment > ---------------------------------------------------------------------------- > > Key: JGRP-2399 > URL: https://issues.jboss.org/browse/JGRP-2399 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Environment: Reproducible both on linux(centos 7.3) and windows 10, my project is using org.eclipse.equinox 3.6.0.v20100503, oracle jdk 1.8.0.212 > Reporter: Orlin Stalyanov > Assignee: Bela Ban > Priority: Major > > {color:#0747A6}Util.java:108 > resource_bundle=ResourceBundle.getBundle("jg-messages",Locale.getDefault(),Util.class.getClassLoader());{color} > is crashing with: > ... > {color:#0747A6}Caused by: java.util.MissingResourceException: Can't find bundle for base name jg-messages, locale en_US > at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1581) > at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1396) > at java.util.ResourceBundle.getBundle(ResourceBundle.java:1091) > at org.jgroups.util.Util.<clinit>(Util.java:108) > ... 162 more{color} > found some relevant info here : https://stackoverflow.com/questions/7564370/importing-resources-from-osgi... > seems like OSGI doesn't really like resources residing in the bundle root ... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4694: -------------------------------- Description: Consume the service provided by DROOLS-4680 and create Data Types in the UI. ⚠️ Notice: - Respect the nesting logic - Use the data types manager for creating type (just like the "Add" button) - The new data types must be added in the end of the list - If a Data Type with the same name already exists, remove it, and add the new one. h2. Manual Scenarios - No fields in data object (/) - Nested data objects, more than 5 levels (/) acceptance criteria updated - Class B extends Class A (/) - Classes added as dependencies (x) we do not follow acceptance criteria - Classes from different package than dmn (/) - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] RHDM-1144 - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] RHDM-1145 - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...], decided to nor report - Import, rename original java class, import again (/) - Import, delete import, import (/) - Import, add field in original java class, import (/) - Import, change field type in original class, import (/) - Import, import (/) - Import, pick also types needed for fields (/) - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] , (/) works in re-review - Use imported type in dmn, test scenario (/) was: Consume the service provided by DROOLS-4680 and create Data Types in the UI. ⚠️ Notice: - Respect the nesting logic - Use the data types manager for creating type (just like the "Add" button) - The new data types must be added in the end of the list - If a Data Type with the same name already exists, remove it, and add the new one. h2. Manual Scenarios - No fields in data object (/) - Nested data objects, more than 5 levels (/) acceptance criteria updated - Class B extends Class A (/) - Classes added as dependencies (x) we do not follow acceptance criteria - Classes from different package than dmn (/) - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - Import, rename original java class, import again (/) - Import, delete import, import (/) - Import, add field in original java class, import (/) - Import, change field type in original class, import (/) - Import, import (/) - Import, pick also types needed for fields (/) - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] - Use imported type in dmn, test scenario (/) > [DMN Designer] BC DOs as DMN DTs - Create import action into the UI > ------------------------------------------------------------------- > > Key: DROOLS-4694 > URL: https://issues.jboss.org/browse/DROOLS-4694 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: convert-15-fields.webm, do-not-pick-fields.webm > > > Consume the service provided by DROOLS-4680 and create Data Types in the UI. > ⚠️ Notice: > - Respect the nesting logic > - Use the data types manager for creating type (just like the "Add" button) > - The new data types must be added in the end of the list > - If a Data Type with the same name already exists, remove it, and add the new one. > h2. Manual Scenarios > - No fields in data object (/) > - Nested data objects, more than 5 levels (/) acceptance criteria updated > - Class B extends Class A (/) > - Classes added as dependencies (x) we do not follow acceptance criteria > - Classes from different package than dmn (/) > - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] RHDM-1144 > - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] RHDM-1145 > - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...], decided to nor report > - Import, rename original java class, import again (/) > - Import, delete import, import (/) > - Import, add field in original java class, import (/) > - Import, change field type in original class, import (/) > - Import, import (/) > - Import, pick also types needed for fields (/) > - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] , (/) works in re-review > - Use imported type in dmn, test scenario (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4694) [DMN Designer] BC DOs as DMN DTs - Create import action into the UI

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4694?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4694: -------------------------------- Description: Consume the service provided by DROOLS-4680 and create Data Types in the UI. ⚠️ Notice: - Respect the nesting logic - Use the data types manager for creating type (just like the "Add" button) - The new data types must be added in the end of the list - If a Data Type with the same name already exists, remove it, and add the new one. h2. Manual Scenarios - No fields in data object (/) - Nested data objects, more than 5 levels (/) acceptance criteria updated - Class B extends Class A (/) - Classes added as dependencies (x) we do not follow acceptance criteria - Classes from different package than dmn (/) - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - Import, rename original java class, import again (/) - Import, delete import, import (/) - Import, add field in original java class, import (/) - Import, change field type in original class, import (/) - Import, import (/) - Import, pick also types needed for fields (/) - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] - Use imported type in dmn, test scenario (/) was: Consume the service provided by DROOLS-4680 and create Data Types in the UI. ⚠️ Notice: - Respect the nesting logic - Use the data types manager for creating type (just like the "Add" button) - The new data types must be added in the end of the list - If a Data Type with the same name already exists, remove it, and add the new one. h2. Manual Scenarios - No fields in data object (/) - Nested data objects, more than 5 levels (x) we do not follow acceptance criteria - Class B extends Class A (/) - Classes added as dependencies (x) we do not follow acceptance criteria - Classes from different package than dmn (/) - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] - Import, rename original java class, import again (/) - Import, delete import, import (/) - Import, add field in original java class, import (/) - Import, change field type in original class, import (/) - Import, import (/) - Import, pick also types needed for fields (/) - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] - Use imported type in dmn, test scenario (/) > [DMN Designer] BC DOs as DMN DTs - Create import action into the UI > ------------------------------------------------------------------- > > Key: DROOLS-4694 > URL: https://issues.jboss.org/browse/DROOLS-4694 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: convert-15-fields.webm, do-not-pick-fields.webm > > > Consume the service provided by DROOLS-4680 and create Data Types in the UI. > ⚠️ Notice: > - Respect the nesting logic > - Use the data types manager for creating type (just like the "Add" button) > - The new data types must be added in the end of the list > - If a Data Type with the same name already exists, remove it, and add the new one. > h2. Manual Scenarios > - No fields in data object (/) > - Nested data objects, more than 5 levels (/) acceptance criteria updated > - Class B extends Class A (/) > - Classes added as dependencies (x) we do not follow acceptance criteria > - Classes from different package than dmn (/) > - Collection fields (x) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] > - simple/built in type java types fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] > - static fields (?) [comment|https://github.com/kiegroup/kie-wb-common/pull/3003#issuecomment-...] > - Import, rename original java class, import again (/) > - Import, delete import, import (/) > - Import, add field in original java class, import (/) > - Import, change field type in original class, import (/) > - Import, import (/) > - Import, pick also types needed for fields (/) > - Import, do not pick types needed for fields (x) [^do-not-pick-fields.webm] > - Use imported type in dmn, test scenario (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4754) Background cell doesn't highlites if passed vallue to DRL returns scenario failure

by Anna Dupliak (Jira)

[ https://issues.jboss.org/browse/DROOLS-4754?page=com.atlassian.jira.plugi... ] Anna Dupliak updated DROOLS-4754: --------------------------------- Sprint: 2019 Week 44-46 (from Okt 28) > Background cell doesn't highlites if passed vallue to DRL returns scenario failure > ---------------------------------------------------------------------------------- > > Key: DROOLS-4754 > URL: https://issues.jboss.org/browse/DROOLS-4754 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > Attachments: Traffic7442357700425429882.tar.xz > > > If the value in Background section made a scenario DRL to fall with exception then the scenario fails and alerts is viewing in alerts table, but the caused cell are not getting red. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4754) Background cell doesn't highlites if passed vallue to DRL returns scenario failure

by Anna Dupliak (Jira)

Anna Dupliak created DROOLS-4754: ------------------------------------ Summary: Background cell doesn't highlites if passed vallue to DRL returns scenario failure Key: DROOLS-4754 URL: https://issues.jboss.org/browse/DROOLS-4754 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.30.0.Final Reporter: Anna Dupliak Assignee: Daniele Zonca Attachments: Traffic7442357700425429882.tar.xz If the value in Background section made a scenario DRL to fall with exception then the scenario fails and alerts is viewing in alerts table, but the caused cell are not getting red. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1901) Upgrade JBoss Modules to 1.9.2.Final

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1901?page=com.atlassian.jira.plugin.s... ] Farah Juma resolved ELY-1901. ----------------------------- Resolution: Done > Upgrade JBoss Modules to 1.9.2.Final > ------------------------------------ > > Key: ELY-1901 > URL: https://issues.jboss.org/browse/ELY-1901 > Project: WildFly Elytron > Issue Type: Component Upgrade > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

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