You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/03/12 07:37:00 UTC

[jira] [Reopened] (MEECROWAVE-104) Prevent Johnzon client jsonbjaxrsprovider to leak used with cxf client

     [ https://issues.apache.org/jira/browse/MEECROWAVE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg reopened MEECROWAVE-104:
--------------------------------------

I'm not a fan of implementing reflection based hacks to work around a broken concept.

This will blow up in our face at some time. And then we will all wonder why the hack we did this.

We should remove it again or at least explicitly document what the class does and describe in the code that it is just a workaround.

 

Another option to probably solve this cleanly: What about adding a `Cache<Config, Jsonb>` to Johnzon? Or even do that at mapper level . The idea is to not end up creating tons of different JohnzonBuilders for exactly the same thingy but only one instance per scenario.

Jsonb instances are reusable anyway.

> Prevent Johnzon client jsonbjaxrsprovider to leak used with cxf client
> ----------------------------------------------------------------------
>
>                 Key: MEECROWAVE-104
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-104
>             Project: Meecrowave
>          Issue Type: Task
>            Reporter: Romain Manni-Bucau
>            Assignee: Romain Manni-Bucau
>            Priority: Major
>             Fix For: 1.2.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)