Hi Sergey, no hurry, with some config it is not a blocker but since I never noticed it in 2.6 as much as in 3.0 I wondered if I missed something.
Great it will get fixed. Thanks! Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-03-23 11:30 GMT+01:00 Sergey Beryozkin <[email protected]>: > Hi Romain > > Good observation, I have this JIRA opened for a while: > > https://issues.apache.org/jira/browse/CXF-4826 > > but I got side-tracked into other work over the time...If > isReadable/isWriteable did not need to have a context info in scope then > services like below would not be affected. You can avoid providers like > JAXBElementProvider called if you add text/plain, etc... > > I've just refreshed it but I'm not sure yet I can fix in time for 3.0.5 > but it is on the map now and we'll take care of it > > Thanks, Sergey > > > On 22/03/15 21:13, Romain Manni-Bucau wrote: > >> Hi guys, >> >> wonder if it would make sense to have a lazy mode >> on org.apache.cxf.jaxrs.utils.InjectionUtils#injectContextMethods. >> >> In my case I use a stupid service: >> >> @Path("simple") >> public class SimpleJaxRs { >> @GET >> public String get() { >> return "it works"; >> } >> } >> >> And I loose a lot of time calling JAXBElementProvider.setMessageContext >> >> Of course I can exclude it but wonder about the default. >> >> wdyt? >> >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <http://rmannibucau.wordpress.com> | Github <https://github.com/ >> rmannibucau> | >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber >> <http://www.tomitribe.com> >> >> >
