[Resteasy-users] Restricting json custom provider to a particular client

Hi Bill, We are using jacksonJsonProvider to consume and produce json data in underscore format. However when we are trying to integrate with 3rd party systems our custom provider is getting called and causing exceptions as 3rd party does not need underscore format. Is there a way to restrict

[Resteasy-users] Fwd: Regarding Ssl handshake during certificate authentication on jboss

Sent from my iPhone Begin forwarded message: From: Date: August 29, 2013, 7:00:06 AM GMT+05:30 To: Bill Burke Cc: Subject: Regarding Ssl handshake during certificate authentication on jboss Hi Bill I have a r

Re: [Resteasy-users] Fwd: Regarding Ssl handshake during certificate authentication on jboss

I have used certs successfully before. On 8/29/2013 9:31 AM, Mukul Panwar wrote: > > > Sent from my iPhone > > Begin forwarded message: > >> *From:* mailto:muku...@hcl.com>> >> *Date:* August 29, 2013, 7:00:06 AM GMT+05:30 >> *To:* Bill Burke mailto:bbu...@redhat.com>> >> *Cc:* >

Re: [Resteasy-users] Restricting json custom provider to a particular client

Not sure what you mean. Which client api are you using? Resteasy 2.3.x or JAX-RS 2.0 in Resteasy 3.0? In the former, you can create/initialize your own ResteasyProviderFactory. In the latter, this automatically happens per Client you create. On 8/29/2013 9:16 AM, Rajshekhar AndalaPisharam w

Re: [Resteasy-users] Fwd: Regarding Ssl handshake during certificate authentication on jboss

Hi Bill I also tried successfully to implement certificate authentication but SsL handshake doing every time of request. Which should reuse the first handshake session. Please suggest about it. Thanks Mukul On Aug 29, 2013, at 7:11 PM, "Bill Burke" wrote: > I have used certs successfully be

Re: [Resteasy-users] Fwd: Regarding Ssl handshake during certificate authentication on jboss

-- Weinan Li On Friday, August 30, 2013 at 12:20 AM, Mukul Panwar wrote: > Hi Bill > > I also tried successfully to implement certificate authentication but SsL > handshake doing every time of request. Which should reuse the first handshake > session. Please suggest about it. Hi Mukul, ar