Re: status 406 from cxf server

Got it to work Finally ! The problem was the inconsistent cxf libraries that were added as dependecies. When I added camel-cxf library as dependecy, maven added various cxf libraries as its dependent, which were older versions. Once I manually updated those indirect dependent jar files the app

Re: status 406 from cxf server

On 01/08/12 22:24, java kurious wrote: The option was supposed to override jersey libraries in Glassfish with the ones in war. Did you try a hint from the CXF wiki on making sure CXF is used for JAX-WS ? This option that you tried first seemed to be the best one, the question is why disabling t

Re: status 406 from cxf server

The option was supposed to override jersey libraries in Glassfish with the ones in war. As a last effort I removed all the jersey related jar files from glassfish/modules directory and Started the glassfish. That made the application work. But, it failed to start the glassfish admin console. But

Re: status 406 from cxf server

Also see this section: http://cxf.apache.org/docs/application-server-specific-configuration-guide.html for what may need to be done to make CXF JAX-WS work on Glassfish Sergey On 01/08/12 12:45, Sergey Beryozkin wrote: Hi On 31/07/12 01:11, java kurious wrote: Hi Sergey, Thanks for bearin

Re: status 406 from cxf server

Hi On 31/07/12 01:11, java kurious wrote: Hi Sergey, Thanks for bearing with me while I try to debug the problem, and help me move further. I disabled the jaxrs library being used by Glassfish by setting following jvm option: -Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs

Re: status 406 from cxf server

Hi Sergey, Thanks for bearing with me while I try to debug the problem, and help me move further. I disabled the jaxrs library being used by Glassfish by setting following jvm option: -Dcom.sun.enterprise.overrideablejavaxpackages=javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext That started to ca

Re: status 406 from cxf server

Ok, I confirmed that it is the problem with Glassfish 3.1. I deployed the same application on Tomcat, and it worked fine even with "text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2" header. Thanks On Thu, Jul 26, 2012 at 7:07 PM, Sergey Beryozkin wrote: > Hi > > On 26/07/12 18:10, java kuri

Re: status 406 from cxf server

Hi On 26/07/12 18:10, java kurious wrote: Hi Sergey, I continue to see the problem with status 406. Is there a way to intercept this request before JAXRSInInterceptor, and change the ACCEPT header ? I've missed your earlier email. I think the fact MediaTypeHeaderProvider is not called indicate

Re: status 406 from cxf server

Hi Sergey, I continue to see the problem with status 406. Is there a way to intercept this request before JAXRSInInterceptor, and change the ACCEPT header ? Thanks for your help. On Thu, Jul 19, 2012 at 6:35 PM, java kurious wrote: > Ok, I have the source code downloaded, and I have the glass

Re: status 406 from cxf server

Hi, On 19/07/12 17:37, java kurious wrote: I am getting following 406 error when sending a request to a REST service. [#|2012-07-19T11:00:50.226-0400|INFO|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=128;_ThreadName=Thread-2;|DEBUG [http-thread-pool-2818