How to check why ByteBuddyInterceptor.intercept is not being called for method call? (the method is package private, not sure if this is important ...)
On Fri, 13 Jan 2023 at 17:30, Maxim Solodovnik <solomax...@gmail.com> wrote: > > Lots of "java.io.NotSerializableException" in such case :((( > Have to check wrapInProxies code ... > > On Fri, 13 Jan 2023 at 17:20, Maxim Solodovnik <solomax...@gmail.com> wrote: > > > > Thanks a lot! > > > > The problem was > > "getComponentInstantiationListeners().add(new > > SpringComponentInjector(this, ctx, true))" > > > > Works for me after changing to be > > "getComponentInstantiationListeners().add(new > > SpringComponentInjector(this, ctx, false))" > > > > investigating :) > > > > On Thu, 12 Jan 2023 at 23:46, Martin Grigorov <mgrigo...@apache.org> wrote: > > > > > > On Thu, Jan 12, 2023, 18:06 Maxim Solodovnik <solomax...@gmail.com> wrote: > > > > > > > Hello All, > > > > > > > > It seems "Injector.get().inject(this);" doesn't work for me as expected > > > > > > > > The bean annotated with @Inject or @SpringBean is injected > > > > > > > > > > Here you say @Inject injects the proxy. > > > > > > (WicketProxy, via ByteBuddy but it differs from what is being injected > > > > by Spring, and all @Inject/@Autowired fields are null :((( > > > > > > > > > > Here it is null... > > > Which one is correct? > > > > > > Or you mean the transitive dependencies are null? If this is the case then > > > debug in SpringBeanLocator. It uses Spring APIs to load the real bean. > > > > > > > > > > > > > What can I troubleshoot? > > > > > > > > -- > > > > Best regards, > > > > Maxim > > > > > > > > > > > > -- > > Best regards, > > Maxim > > > > -- > Best regards, > Maxim -- Best regards, Maxim