[
https://issues.apache.org/jira/browse/ATLAS-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16688558#comment-16688558
]
Pierre Padovani commented on ATLAS-2249:
----------------------------------------
My apologies for taking so long to answer this it got buried in email. I would
actually not recommend using this patch due to an issue in terms of json
serialization around nulls we discovered. Our solution/workaround was to
uber-jar the client changing all of the packaging of the underlying Jersey 1
code to avoid conflicts.
I believe that only by updating the entire Atlas code base to Jersey 2 can this
be resolved in a correct manner.
> Upgrade Atlas Client to use Jersey 2
> ------------------------------------
>
> Key: ATLAS-2249
> URL: https://issues.apache.org/jira/browse/ATLAS-2249
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-intg
> Affects Versions: 1.0.0
> Reporter: Pierre Padovani
> Priority: Major
> Labels: patch-available
> Attachments: client-jersey2-V2.patch, client-jersey2-V3.patch,
> client-jersey2-V4.patch, client-jersey2.patch
>
>
> Using the existing Atlas client within a Jersey 2 service causes conflicts. I
> recommend upgrading just the client code to Jersey 2. The enclosed patch
> fully upgrades the V1 and V2 client to Jersey 2, and we have tested this
> against our own installation of 1.0.0-SNAPSHOT.
> NOTE: We have not tested SSL/Kerberos authentication/security
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
