You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/05/17 00:04:00 UTC

[jira] [Updated] (ATLAS-2249) Upgrade Atlas Client to use Jersey 2

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

Madhan Neethiraj updated ATLAS-2249:
------------------------------------
    Fix Version/s:     (was: 1.0.0)

> 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)