February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3605) Invalid DMN file after migration 1.1 -> 1.2

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3605?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-3605: ---------------------------------------- I'd guess the reference to {{kie.tSalary}} on the {{InputData}} and {{Decision}} are wrong. > Invalid DMN file after migration 1.1 -> 1.2 > ------------------------------------------- > > Key: DROOLS-3605 > URL: https://issues.jboss.org/browse/DROOLS-3605 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Attachments: dmn-daniele_after.dmn, dmn-daniele_before.dmn > > > `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error > [KBase: defaultKieBase]: DMN: Unable to resolve type reference 'kie.tSalary' on node 'Yearly Salary' (resource: com/dmn-daniele.dmn, DMN id: _8B521A18-C356-44D4-BEF0-123676DEDEE0, The listed type definition was not found) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3605) Invalid DMN file after migration 1.1 -> 1.2

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3605?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3605: --------------------------------------- [~tari_manga] FYI > Invalid DMN file after migration 1.1 -> 1.2 > ------------------------------------------- > > Key: DROOLS-3605 > URL: https://issues.jboss.org/browse/DROOLS-3605 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Attachments: dmn-daniele_after.dmn, dmn-daniele_before.dmn > > > `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error > [KBase: defaultKieBase]: DMN: Unable to resolve type reference 'kie.tSalary' on node 'Yearly Salary' (resource: com/dmn-daniele.dmn, DMN id: _8B521A18-C356-44D4-BEF0-123676DEDEE0, The listed type definition was not found) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3605) Invalid DMN file after migration 1.1 -> 1.2

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3605?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3605: ---------------------------------- Description: `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error [KBase: defaultKieBase]: DMN: Unable to resolve type reference 'kie.tSalary' on node 'Yearly Salary' (resource: com/dmn-daniele.dmn, DMN id: _8B521A18-C356-44D4-BEF0-123676DEDEE0, The listed type definition was not found) was: `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error > Invalid DMN file after migration 1.1 -> 1.2 > ------------------------------------------- > > Key: DROOLS-3605 > URL: https://issues.jboss.org/browse/DROOLS-3605 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniele Zonca > Assignee: Michael Anstis > Priority: Major > Attachments: dmn-daniele_after.dmn, dmn-daniele_before.dmn > > > `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error > [KBase: defaultKieBase]: DMN: Unable to resolve type reference 'kie.tSalary' on node 'Yearly Salary' (resource: com/dmn-daniele.dmn, DMN id: _8B521A18-C356-44D4-BEF0-123676DEDEE0, The listed type definition was not found) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3605) Invalid DMN file after migration 1.1 -> 1.2

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3605: ------------------------------------- Summary: Invalid DMN file after migration 1.1 -> 1.2 Key: DROOLS-3605 URL: https://issues.jboss.org/browse/DROOLS-3605 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Daniele Zonca Assignee: Michael Anstis Attachments: dmn-daniele_after.dmn, dmn-daniele_before.dmn `dmn-daniele_before.dmn` is a simple 1.1 DMN file. After migration (`dmn-daniele_after.dmn`) DMN model compilation fails with this error -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

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

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-10728?page=com.atlassian.jira.plugin... ] Alessio Soldano closed WFLY-10728. ---------------------------------- Resolution: Out of Date > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-377) Research Openshift Flexy Installer As OSOOS Replacement

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-377?page=com.atlassian.jira.plugin.... ] Matt Mahoney closed SWSQE-377. ------------------------------ Resolution: Done > Research Openshift Flexy Installer As OSOOS Replacement > ------------------------------------------------------- > > Key: SWSQE-377 > URL: https://issues.jboss.org/browse/SWSQE-377 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > > OSOOS will be decommissioned at some point. The Openshift flexy installer is 'said' to be able to install onto Openstack. Thus this task is to research OS Flexy installer to determine if it can be used as an OSOOS replacement. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3906) Upgrade JBoss Modules to 1.8.6.Final

by David Lloyd (Jira)

[ https://issues.jboss.org/browse/WFCORE-3906?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-3906: ------------------------------------- There are never any plans, but if you want a release, feel free to give me a ping on chat or email. > Upgrade JBoss Modules to 1.8.6.Final > ------------------------------------ > > Key: WFCORE-3906 > URL: https://issues.jboss.org/browse/WFCORE-3906 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Modules > Reporter: David Lloyd > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3604) Improvements of table/column width

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3604?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3604: --------------------------------- Tester: Klara Kufova > Improvements of table/column width > ---------------------------------- > > Key: DROOLS-3604 > URL: https://issues.jboss.org/browse/DROOLS-3604 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Remaining from https://issues.jboss.org/browse/DROOLS-3377 > - Horizontal scrollbar does not disappear even after resizing the last column to the proper width. > - Width is restored as default when user set the binding of a column. This happens only if he already changed manually the width -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3482) Terminology for DMN import

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3482?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3482: ------------------------------------- Thank you [~stetson.robinson] > Terminology for DMN import > -------------------------- > > Key: DROOLS-3482 > URL: https://issues.jboss.org/browse/DROOLS-3482 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Stetson Robinson > Priority: Minor > Labels: drools-tools > > Define best term to use for importing a DMN file, from the project directory. Importing a .dmn file will include file nodes, data types, etc. The term will be used for a tab label, button labels, and the like. > UX mockups currently use "import" but other terms such as "include" have been discussed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-586) Switch kiali-qe-utils repository into GitLab

by Jeeva Kandasamy (Jira)

Jeeva Kandasamy created SWSQE-586: ------------------------------------- Summary: Switch kiali-qe-utils repository into GitLab Key: SWSQE-586 URL: https://issues.jboss.org/browse/SWSQE-586 Project: Kiali QE Issue Type: QE Task Reporter: Jeeva Kandasamy Assignee: Michael Foley Looks like internal GitLab[1] is ready to use. We can move our kiali-qe-utils[2] to GitLab Why? * GitLab looks cool * Friendly web code browser * Review PR's * integrate with CI (if needed) * improves collaboration We should get others feedback in our team on this task. [1] - https://gitlab.cee.redhat.com [2] - http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 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