August 2018 - jboss-jira - Jboss List Archives

[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ý updated WFLY-10728: --------------------------------- Attachment: single-application.zip > 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 > Attachments: 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.5.0#75005)

6 years, 5 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ý edited comment on WFLY-10728 at 8/2/18 1:57 AM: -------------------------------------------------------------- [~gwsch], [~asoldano], [~ron_sigal]: I don't have implementation of RenderObject and Link. But I made small workaround for that and I'm unable to reproduce this on WF13/WF master. I prepared test application, GET request for {{http://localhost:8080/jaxrs-wf/a/d}} should test it, but it passed - [^single-application.zip]. Can you please test this on WildFly prepared from master github branch? Some fixes of JSON were made after WF13 release, so these fixes were not released yet (RESTEASY-1911, [doc|https://github.com/resteasy/Resteasy/commit/f6ddef5accb88d924e3d14ab1...]). was (Author: mkopecky): [~gwsch], [~asoldano], [~ron_sigal]: I don't have implementation of RenderObject and Link. But I made small workaround for that and I'm unable to reproduce this on WF13/WF master. I prepared test application, GET request for {{http://localhost:8080/jaxrs-wf/a/d}} should test it, but it passed. Can you please test this on WildFly prepared from master github branch? Some fixes of JSON were made after WF13 release, so these fixes were not released yet (RESTEASY-1911, [doc|https://github.com/resteasy/Resteasy/commit/f6ddef5accb88d924e3d14ab1...]). > 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 > Attachments: 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.5.0#75005)

6 years, 5 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: -------------------------------------- [~gwsch], [~asoldano], [~ron_sigal]: I don't have implementation of RenderObject and Link. But I made small workaround for that and I'm unable to reproduce this on WF13/WF master. I prepared test application, GET request for {{http://localhost:8080/jaxrs-wf/a/d}} should test it, but it passed. Can you please test this on WildFly prepared from master github branch? Some fixes of JSON were made after WF13 release, so these fixes were not released yet (RESTEASY-1911, [doc|https://github.com/resteasy/Resteasy/commit/f6ddef5accb88d924e3d14ab1...]). > 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 > Attachments: User.java, UserQueryForm.java, UsersApi.java > > > 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.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2808) [Guided Decision Table] Dependent enums are not loaded

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2808: -------------------------------- Priority: Minor (was: Major) > [Guided Decision Table] Dependent enums are not loaded > ------------------------------------------------------ > > Key: DROOLS-2808 > URL: https://issues.jboss.org/browse/DROOLS-2808 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: Car.java, Screenshot from 2018-07-31 12-00-11.png, prices.enumeration > > > The guided decision table doesn't load dependent enums. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2808) [Guided Decision Table] Dependent enums are not loaded

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2808?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2808: -------------------------------- Affects Version/s: 7.9.0.Final > [Guided Decision Table] Dependent enums are not loaded > ------------------------------------------------------ > > Key: DROOLS-2808 > URL: https://issues.jboss.org/browse/DROOLS-2808 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > Attachments: Car.java, Screenshot from 2018-07-31 12-00-11.png, prices.enumeration > > > The guided decision table doesn't load dependent enums. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2825) Drools @Expires is not working with x seconds 7.4.1 Final Drools version

by Srinivas ev (JIRA)

Srinivas ev created DROOLS-2825: ----------------------------------- Summary: Drools @Expires is not working with x seconds 7.4.1 Final Drools version Key: DROOLS-2825 URL: https://issues.jboss.org/browse/DROOLS-2825 Project: Drools Issue Type: Bug Affects Versions: 7.4.1.Final Reporter: Srinivas ev Assignee: Mario Fusco Fix For: 7.4.1.Final Attachments: EvictionTest.zip, heap.PNG Attached reproducer. Please check once, I inserted 5 Fact POJO's. It should have deleted after 200s based on declaration in the rule file. declare Fact @role( event ) @expires(200s) end Heap dump shows the 5 entries even after I took the heap dump after 10 minutes. Please let me know regarding this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2824) Add listener support for context entry evaluation

by Edson Tirelli (JIRA)

Edson Tirelli created DROOLS-2824: ------------------------------------- Summary: Add listener support for context entry evaluation Key: DROOLS-2824 URL: https://issues.jboss.org/browse/DROOLS-2824 Project: Drools Issue Type: Enhancement Components: dmn engine Affects Versions: 7.9.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 7.10.0.Final >From Simon: ----------- We are starting to have a lot of clients asking for the ability to see the result of boxed context rows inside. Right now, we have only the result being returned (and if there is no return, we get the context). We already are hook on the DMNRuntimeEventListener for afterEvaluateDecisionTable, would it be possible to have another method added on that listener that would notify when a context entry was evaluated with the result? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2823) FEEL Parser: `not` breaks with `list contains`

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2823?page=com.atlassian.jira.plugi... ] Edson Tirelli reassigned DROOLS-2823: ------------------------------------- Assignee: Edoardo Vacchi (was: Edson Tirelli) > FEEL Parser: `not` breaks with `list contains` > ----------------------------------------------- > > Key: DROOLS-2823 > URL: https://issues.jboss.org/browse/DROOLS-2823 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > > *list contains([1,2,3,4,5,6], 3)* returns true > *not(list contains([1,2,3,4,5,6], 3))* returns “list contains([1,2,3,4,5,6], 3)”, it should return false > Most likely related to an issue with the parse tree branches -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2815) [DMN Designer] Make Expression Type dependent on Diagram Node

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2815?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-2815: --------------------------------------- Regarding allowing a Decision node to have a function expression, the spec allows it, but it is quite an edge case. I would restrict this if and only if it makes the implementation of the editor easier. A BKM on the other hand is *ALWAYS* a function definition, but remember that the body of a function definition can be any of the valid expression types supported by DMN: decision table, literal, context, invocation, list, relation or function definition (although this one can probably be filtered out, as it is even more of an edge case). > [DMN Designer] Make Expression Type dependent on Diagram Node > ------------------------------------------------------------- > > Key: DROOLS-2815 > URL: https://issues.jboss.org/browse/DROOLS-2815 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > > The expression editor options should be dependent on the diagram node type. > h2. Decision Node > Should allow all expression types except of *Function* > h2. BKM Node > Should allow only *Function* expression type. > h3. Further improvement > BKM node has automatically function expression inside - separate jira, or won't be implemented? > ([~jomarko] IMO If/when [~tirelli] confirms the subject of this JIRA is the expected/required operation I'd ensure BKMs have a Function set and cannot be cleared). > h2. Acceptance tests > - Not possible to set *function expression type* for Decision node > - Possible to set just *function expression type* for BKM node > -- Created automatically if we decide to implement here > - Dialog shown if opened file from external tool that doesn't follow this restriction -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-365) Update B18 to Openshift 3.10

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-365?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-365: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Update B18 to Openshift 3.10 > ---------------------------- > > Key: SWSQE-365 > URL: https://issues.jboss.org/browse/SWSQE-365 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 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 August 2018