| [che-dev] Using a JAX-RS client library in Che |
|
Hi, I'm inspecting the area of issuing outgoing HTTP calls from inside Che. We are in a more advanced position now - ditching HttpJsonHelper and replacing it with HttpJsonRequest. But we still have the issue
of managing general (non JSON) HTTP requests. Currently we have numerous areas in Che code (both 3.x and 4.x) that create and manipulate URLConnection. Lots of code duplication no central management/filtering.
I would like to provide a POC for a general "request factory" that provides and manages standard JAX-RS targets. https://docs.oracle.com/javaee/7/api/javax/ws/rs/client/package-summary.html HttpJsonRequest will keep its API but use the more general APIs internally, eventually having a single flow for all out-going HTTP
requests in Che. Since Everrest provides server-side JAX-RS only, I have to use one of the available JAX-RS client libraries.
Is it OK to add Jersey Client and use it from Che ? https://jersey.java.net/documentation/latest/client.html thank you Tareq Sharafy Cloud Development Experience | SAP Labs Israel | 15 Hatidhar st, Raanana 43665, Israel T +972-(0)7-4732-1647
| F +972-(0)9-777-5618 |