[ 
https://issues.apache.org/jira/browse/JOHNZON-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360871#comment-17360871
 ] 

Markus Karg commented on JOHNZON-345:
-------------------------------------

Actually I mean literally JSON-P. The point is, we have to fix _this_ issue on 
an application which must run on Payara 4. Payara 4 comes with JSON-P 1.0 and 
forbids to replace it. Johnzon 1.1 works fine on JSON-P 1.1, but since Johnzon 
1.2 it calls a parser method only existing in JSON-P 1.2. That's why I cannot 
simply step up to Johnzon 1.2+, but need to patch Johnzon 1.1.

Thanks, will ask a colleague to bisect. ;)

> StackOverflow when serializing Collection<URL>
> ----------------------------------------------
>
>                 Key: JOHNZON-345
>                 URL: https://issues.apache.org/jira/browse/JOHNZON-345
>             Project: Johnzon
>          Issue Type: Bug
>          Components: JSON-B
>    Affects Versions: 1.2.11
>            Reporter: Markus Karg
>            Priority: Blocker
>             Fix For: 1.2.12
>
>
> The JSON-B specification mandates that compliant implementations MUST support 
> serialization of Collection and URL.
> Unfortunately when serializing a Collection<URL> using Johnzon-Jsonb 1.2.11 
> an infinite loop happens, resulting in a StackOverflowException.
> I have reproduced this complaint by the following code:
> {{  JsonbConfig jsonbConfig = new JsonbConfig();}}
>  {{  Jsonb jsonb = JsonbBuilder.create(jsonbConfig);}}
>  {{  URL url = new URL("http://www.apache.org";);}}
>  {{  Collection<URL> collection = Collections.singleton(url);}}
>  {{  System.out.println("Jsonb collection: " + jsonb.toJson(collection));}}
> The same problem occurs with Collection<URI>, too.
> Collections in general work fine, i. e. the problem does not occur with e. g. 
> Collection<UUID> or Collection<String>. Also single URL and URIs objects work 
> fine, i. e. when not inside a collection!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to