Some comments still said that including the maven artifact,
jersey-media-json-jackson, could override gson behavior, but
that is no longer true. The comments have been removed.
Change-Id: I9b6477b76f835b96c52ccb9777b80791fc6b1d77
Issue-ID: POLICY-1428
Signed-off-by: Jim Hahn <jrh3@att.com>
/**
* Http Client implementation using a Jersey Client.
- *
- * <p>Note: the serialization provider will be ignored if the maven artifact,
- * <i>jersey-media-json-jackson</i>, is included, regardless of whether it's included
- * directly or indirectly.
*/
public class JerseyClient implements HttpClient {
* {@link #addServletClass(String, String)} is used or
* {@link #addServletPackage(String, String)} is used. Thus it's possible to have both the
* server's class provider property and the server's package provider property populated.
- *
- * <p>Also note: the serialization provider will be ignored if the maven artifact,
- * <i>jersey-media-json-jackson</i>, is included, regardless of whether it's included
- * directly or indirectly.
*/
public class JettyJerseyServer extends JettyServletServer {