Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Subject: Re: arrayKeys and serializeAsArray support
To: users@cxf.apache.org
References: <1468260179061-5770305.post@n5.nabble.com>
From: Sergey Beryozkin <sberyozkin@gmail.com>
Message-ID: <5783ECFE.3050706@gmail.com>
Date: Mon, 11 Jul 2016 22:01:18 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <1468260179061-5770305.post@n5.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Jul 2016 19:01:59 -0000

Hi
On 11/07/16 21:02, M.Ismail wrote:
> Hi,
>
> I am using camel 2.13 and CXF 2.7.7 and I am using the workaround
> serializeAsArray and arrayKeys to solve the single item array issue.
> However, the webservice specs that I call have changed and I can this
> workaround isn't applicable anymore. What are my options now?
Why it is not applicable any longer ?
>
> 1- Can I use the Jackson provider if it doesn't have this single item array
> issue?
Sure, try it if you'd like
> 2- Should I use a custom mapper for the exception case that prevented me to
> use arrayKeys? If so can you please, provide a sample?
>
In general you can register an exception mapper for any exception that 
will escape without this mapper

Cheers, Sergey
> Regards,
> Ismail
>
>
>
> --
> View this message in context: http://cxf.547215.n5.nabble.com/arrayKeys-and-serializeAsArray-support-tp5770305.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>