Skip to main content

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

  • From: "Oliver B. Fischer" <mailsink@...>
  • To: users@...
  • Subject: Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0
  • Date: Wed, 21 Aug 2013 23:26:02 +0200

Hi Pavel,

I set the property, but still get an 500 without any trace in the log files.

Thanks for the hint with the logger. I can now see the registered providers. My one is also listet. Does the order matter?

Best,

Oliver



Am 21.08.13 15:47, schrieb Pavel Bucek:
please see
https://jersey.java.net/apidocs/latest/jersey/javax/ws/rs/core/Application.html#getProperties()


in short - if you are working with Application (or ResourceConfig)
directly, you can set it there, if not, use init or context param,
something like:


     <servlet>
         ...
         <init-param>
<param-name>jersey.config.workers.legacyOrdering</param-name>
             <param-value>true</param-value>
         </init-param>
         ...
     </servlet>


JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/21/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Pavel Bucek 08/21/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/21/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Pavel Bucek 08/21/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/21/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Pavel Bucek 08/22/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/22/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/22/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Pavel Bucek 08/23/2013

Re: JAX-RS broken when migrating from 3.1.2.2 to 4.0

Oliver B. Fischer 08/23/2013
 
 
Close
loading
Please Confirm
Close