[
https://issues.apache.org/jira/browse/MEECROWAVE-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394927#comment-16394927
]
Romain Manni-Bucau commented on MEECROWAVE-104:
-----------------------------------------------
hmm, there is no real reflection here at design level Mark - just the one to
exclude our own subclass of johnzon we can drop not using inheritance but
composition - and it is not a workaround but the way to integrate johnzon and
cxf together properly making both lifecycles aligned in usages.
thought about the cache when implementing johnzon and really thought it was a
no go since it requires an eviction thread to make any sense.
If you think about reusing the same instances by config it doesn't work since
you have to release the cdi beans at close() time and this is what the user
expects. A valid usage is to have a dependent adapter and a per thread caching
in user codebase, this would be broken with your cache for instance.
> 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)
