February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2609) Implement decision table analysis as DMN validator extension

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-2609?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2609: ----------------------------------- Sprint: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01 (was: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07) > Implement decision table analysis as DMN validator extension > ------------------------------------------------------------ > > Key: DROOLS-2609 > URL: https://issues.jboss.org/browse/DROOLS-2609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Fedor Gavrilov > Assignee: Matteo Mortari > Priority: Major > Attachments: Algorithms for Decision Table Analysis.docx > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11653) Kabir Demo

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11653?page=com.atlassian.jira.plugin... ] Kabir Khan deleted WFLY-11653: ------------------------------ > Kabir Demo > ---------- > > Key: WFLY-11653 > URL: https://issues.jboss.org/browse/WFLY-11653 > Project: WildFly > Issue Type: Feature Request > Reporter: Kabir Khan > Assignee: Kabir Khan > Priority: Major > > Don't touch!!! I need this for a demo at the F2F -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11668) Core queue creation is missing a routing type attribute

by ehsavoie Hugonnet (Jira)

ehsavoie Hugonnet created WFLY-11668: ---------------------------------------- Summary: Core queue creation is missing a routing type attribute Key: WFLY-11668 URL: https://issues.jboss.org/browse/WFLY-11668 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 15.0.1.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet deploying a queue and jms queue that map to the same address like bellow: <queue name="jms.queue.SSOQueue" address="jms.queue.SSOQueue" durable="true"/> <jms-queue name="SSOQueue" entries="/queue/SSOQueue java:jboss/exported/jms/queue/SSOQueue"/> Throws the following error: AMQ222275: Failed to deploy queue jms.queue.SSOQueue: Can't update queue jms.queue.SSOQueue with routing type: MULTICAST, Supported routing types for address: jms.queue.SSOQueue are [ANYCAST] This is due to Artemis 2.6.x upgrade -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11648) Upgrade to RESTEasy 3.6.3.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11648?page=com.atlassian.jira.plugin... ] Alessio Soldano commented on WFLY-11648: ---------------------------------------- [~mkopecky] , we should have 3.6.3 released in a couple of weeks from now, so we'll try including it in WF16; being it a micro release, we can afford upgrading just after the feature freeze (checked with Kabir). > Upgrade to RESTEasy 3.6.3.Final > ------------------------------- > > Key: WFLY-11648 > URL: https://issues.jboss.org/browse/WFLY-11648 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Marek Kopecký > Assignee: Alessio Soldano > Priority: Critical > Fix For: 16.0.0.Beta1 > > > Upgrade to RESTEasy 3.6.3.Final > cc [~jbliznak], [~tterem] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

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

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3523?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-3523: -------------------------------- Sprint: 2019 Week 05-07 > 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: Mario Fusco > 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=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)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-306) Update add-user to use AESH or move it into the CLI

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFCORE-306?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFCORE-306: --------------------------------- Component/s: (was: Scripts) > Update add-user to use AESH or move it into the CLI > --------------------------------------------------- > > Key: WFCORE-306 > URL: https://issues.jboss.org/browse/WFCORE-306 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Darran Lofthouse > Assignee: Jean-Francois Denise > Priority: Major > > Within the add-user utility it is difficult to handle situations where we do not have access to a java.io.Console which is the easiest way to handle password reading without an echo to the user e.g. in Cygwin > Switching to AESH would allow us to use the implementation there to handle this. > Alternatively it may actually make sense to make add-user a special mode of the CLI, we may at some point want to switch to runtime operations being executed on the server so porting to the CLI could be the first step to make this possible. > Overall this is going to require further discussion so the comments here are just a starting point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10743) Java Agent using JUL causes JBoss LogManager issues

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-10743?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFLY-10743: --------------------------------- Component/s: Logging > Java Agent using JUL causes JBoss LogManager issues > --------------------------------------------------- > > Key: WFLY-10743 > URL: https://issues.jboss.org/browse/WFLY-10743 > Project: WildFly > Issue Type: Enhancement > Components: Logging, Scripts > Affects Versions: 13.0.0.Final > Reporter: Brad Maxwell > Priority: Major > > To workaround the issue, these steps are required below. It would be better if we could handle this in the scripts or another way such that the user did not have to directly reference the current jboss-logmanager jar. > {code} > JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" > JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-<version>.jar" > {code} > {code} > if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then > JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager" > fi > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10728) RESTEASY008200: JSON Binding deserialization error for valid JSON

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-10728?page=com.atlassian.jira.plugin... ] Marek Kopecký commented on WFLY-10728: -------------------------------------- bq. Looks like is issue is not reproducable anymore. [~ron_sigal]: Can you close this issue now? if [~gwsch] still see this issue, he can reopen it with reproducer. Btw, RESTEASY-2106 add better exception messages + print stacktrace > RESTEASY008200: JSON Binding deserialization error for valid JSON > ----------------------------------------------------------------- > > Key: WFLY-10728 > URL: https://issues.jboss.org/browse/WFLY-10728 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 13.0.0.Final > Environment: JDK-10.0.1 > Reporter: Guido Schmidt > Assignee: Ron Sigal > Priority: Major > Attachments: TestRestEasy.war, User.java, UserQueryForm.java, UsersApi.java, single-application.zip > > > I found the following regression issue running the code inside an ejb jar: > In the context of a search for a user for a user via the Wordpress REST API, I get e.g. following String: > {code:JavaScript} > {{[{ > "id": 15, > "username": "wpx1", > "name": "Word Press1", > "first_name": "Word", > "last_name": "Press1", > "email": "wpx1(a)pb.com", > "url": "", > "description": "", > "link": "http:\/\/www.pbpiazza.com\/dayc\/archives\/author\/wpx1", > "locale": "en_US", > "nickname": "wpx1", > "slug": "wpx1", > "roles": ["contributor"], > "registered_date": "2018-07-23T08:59:13+00:00", > "capabilities": { > "edit_posts": true, > "read": true, > "level_1": true, > "level_0": true, > "delete_posts": true, > "manage_bookings": true, > "upload_event_images": true, > "delete_events": true, > "edit_events": true, > "read_private_events": true, > "delete_recurring_events": true, > "edit_recurring_events": true, > "edit_locations": true, > "read_private_locations": true, > "read_others_locations": true, > "contributor": true > }, > "extra_capabilities": { > "contributor": true > }, > "avatar_urls": { > "24": "http:\/\/1.gravatar.com\/avatar\/a4d79ad5a72a13f7d7739c9a3dd9a17b?s=24&d=mm&r=g", > "48": "http:\/\/1.gravatar.com\/avatar\/a4d79ad5a72a13f7d7739c9a3dd9a17b?s=48&d=mm&r=g", > "96": "http:\/\/1.gravatar.com\/avatar\/a4d79ad5a72a13f7d7739c9a3dd9a17b?s=96&d=mm&r=g" > }, > "meta": [], > "_links": { > "self": [{ > "href": "http:\/\/www.pbpiazza.com\/dayc\/wp-json\/wp\/v2\/users\/15" > } > ], > "collection": [{ > "href": "http:\/\/www.pbpiazza.com\/dayc\/wp-json\/wp\/v2\/users" > } > ] > } > } > ]}} > {code} > This is achieved by a call of the UsersApi method listUsersAsString: > > ResteasyWebTarget target = (ResteasyWebTarget)restEasy.target(uri); > target.proxy(UsersApi.class); > The call rendering the result into a List<User> fails with error message in the subject. > The result is perfectly fine running Wildfly 11.Plain test cases with Wildfly 13 libraries is also fine. It seems to be a runtime configuration issue of RESTEasy in WIldfly 13. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11648) Upgrade to RESTEasy 3.6.3.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11648?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-11648: ----------------------------------- Fix Version/s: 16.0.0.Beta1 > Upgrade to RESTEasy 3.6.3.Final > ------------------------------- > > Key: WFLY-11648 > URL: https://issues.jboss.org/browse/WFLY-11648 > Project: WildFly > Issue Type: Component Upgrade > Components: REST > Reporter: Marek Kopecký > Assignee: Alessio Soldano > Priority: Critical > Fix For: 16.0.0.Beta1 > > > Upgrade to RESTEasy 3.6.3.Final > cc [~jbliznak], [~tterem] -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2609) Implement decision table analysis as DMN validator extension

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-2609?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2609: ----------------------------------- Sprint: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01, 2019 Week 05-07 (was: 2018 Week 48-50, 2019 Week 02-04, 2018 Week 51-01) > Implement decision table analysis as DMN validator extension > ------------------------------------------------------------ > > Key: DROOLS-2609 > URL: https://issues.jboss.org/browse/DROOLS-2609 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Fedor Gavrilov > Assignee: Matteo Mortari > Priority: Major > Attachments: Algorithms for Decision Table Analysis.docx > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2019