Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5F59111440 for ; Thu, 4 Sep 2014 20:25:24 +0000 (UTC) Received: (qmail 54481 invoked by uid 500); 4 Sep 2014 20:25:24 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 54446 invoked by uid 500); 4 Sep 2014 20:25:24 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 54435 invoked by uid 99); 4 Sep 2014 20:25:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Sep 2014 20:25:24 +0000 Date: Thu, 4 Sep 2014 20:25:24 +0000 (UTC) From: "Srinivas Nagulapalli (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-5988) Provide support for a pluggable parameter conversion mechanism for JAX-RS client side proxies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Srinivas Nagulapalli created CXF-5988: ----------------------------------------- Summary: Provide support for a pluggable parameter conversion = mechanism for JAX-RS client side proxies Key: CXF-5988 URL: https://issues.apache.org/jira/browse/CXF-5988 Project: CXF Issue Type: Bug Components: Core, JAX-RS Affects Versions: 3.0.1 Environment: Windows 7 Reporter: Srinivas Nagulapalli Fix For: 3.0.1 Server-side JAX-RS implementation allows injection of custom parameter conv= erters using ParamConverterProvider (http://cxf.apache.org/docs/jax-rs-basi= cs.html#JAX-RSBasics-Parameterconverters). A similar mechanism (or the exact same) is required on the client side to c= ontrol how parameters are serialized (marshalled). One approach is to allow= specifying param converters when declaring jaxrs:client with Spring and/or= programmatically specifying it.=20 A specific case to consider: Client side serialization of Date object (java= .util.Date).=20 Given the following API: @Path(=E2=80=9C/someresource=E2=80=9D) @GET void someApi(@MatrixParam(=E2=80=9C=E2=80=9D) SomeRequestWithDate request); =20 Following shows the structure of the request with Dates: //---------------------------------------------------- import java.util.Date; public class SomeRequestWithDate {=09 protected Date startDate; =09 public Date getStartDate() { return startDate; } } //---------------------------------------------------- When API is invoked through a client proxy Then the following URL should be generated (where dates are serialized as I= SO strings): /someresource/;startDate=3D2014-09-04T19:05:38.785Z Instead, currently following URL is generated: /someresource/;startDate.date=3D4;startDate.hours=3D15;startDate.minutes=3D= 4;startDate.month=3D8;startDate.seconds=3D34;startDate.time=3D1409857474660= ;startDate.year=3D114;startDate.day=3D4;startDate.timezoneOffset=3D240 -- This message was sent by Atlassian JIRA (v6.3.4#6332)