Hi. I just wanted to confirm, that the changes you made did the trick!
Thanks! Veit Gesendet: Freitag, 23. Januar 2015 um 18:12 Uhr Von: "Sergey Beryozkin" <[email protected]> An: [email protected] Betreff: Re: Aw: Re: Re: client proxy conversion after request leads to NPE On 23/01/15 16:30, Sergey Beryozkin wrote: > Hi > > I've pushed the following change: > > http://git-wip-us.apache.org/repos/asf/cxf/commit/be929cdc > > This is the only thing which is different from the top level proxy > creation code. If it helps then it is OK. I'm not really keen to > investigate why having Spring dependencies might have side-effects on > Java Proxy functioning properly :-). > > Actually, just few days I added a system property disabling Spring in > CXF class helpers. Perhaps there are some interferences at that level. > Setting an "org.apache.cxf.useSpringClassHelpers" system property to > true would disable Spring in that context - please also experiment with > this property Sorry. it has to be set to false if disabling Spring level support is needed Cheers, Sergey > Thanks, Sergey > > On 23/01/15 14:52, Veit Guna wrote: >> Ok. Meanwhile I tracked down the problem. As I thought before, it is >> spring related! >> I sent you a testcase which reproduces the problem. Maybe it helps to >> find the problem. >> >> Thanks! >> Veit >> >> >> Gesendet: Freitag, 23. Januar 2015 um 15:22 Uhr >> Von: "Sergey Beryozkin" <[email protected]> >> An: [email protected] >> Betreff: Re: Aw: Re: client proxy conversion after request leads to NPE >> On 23/01/15 14:18, Veit Guna wrote: >>> >>> >>> Hm. It seems it has also something todo with dependencies on my >>> classpath. On the first look, it seems that spring is somehow >>> involved in the problem. >>> If I remove some deps, it works, if I add them, it breaks again. So >>> maybe let me look a bit further, before you fix something that maybe >>> isn't broken :). >>> >> Sure, I thought it was strange that with your earlier issue we could not >> see Client casted to InvocationHandlerAware even though both interfaces >> are provided at the proxy creation time. >> That said, I'll need to align in because if subresource is an abstract >> or concrete class than it is a CGLIB turn and InvocationHandlerAware >> would be needed, I see it is not provided to the proxy creation code >> >> Sergey >> >> > >
