Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hello Martin, it is: personenProvider = (com.sun.proxy.$Proxy24) org.apache.wicket.proxy.LazyInitProxyFactory$JdkHandler@6eb3b9ea wrapInProxies is true I added a SignIn mechanism, SignInSession uses PersonenDao too to authorize in the database. But I checked not to have any references to it,

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hi, Put a breakpoint at PersonenTable constructor and see what is the type of ' personenProvider'. It must be JDK Proxy instance. If it is not then something wrong is going on. org.apache.wicket.guice.GuiceComponentInjector#GuiceComponentInjector(org.apache.wicket.Application,

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hi Bas, I put it in http://pastie.org/private/19zeomb8uy1beb1gfjegq I fear it is not really useful, since it starts with org.apache.wicket.WicketRuntimeException: A problem occurred while trying to collect debug information about not serializable object Dieter Am 15.06.2016 um 13:39 schrieb

Re: wicket 1.4.12 https issue - Is it a wicket version compatibility issue with the other software's?

Thank you Martin! let me try with 6.x or 7.x. On Wed, Jun 15, 2016 at 3:28 AM, Martin Grigorov wrote: > Hi, > > Wicket 1.4.x and 1.5.x use vanilla JavaScript for the Ajax stuff. > Since Wicket 6.x we use jQuery for better browser compatibility. > Try with Wicket

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hi Dieter, Can you share the stack trace of the serialization checker error? Normally it points out where in the hierarchy it found a non-serializable object. My first guess is that you are referencing the dao class somewhere directly from your page. The stack trace will prove me right or wrong

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Hello Bas, I try to cut small pieces of the code, please tell me if you want to see more. First the error: 12:59:03.919 [http-nio-8084-exec-6] WARN o.a.w.c.u.o.c.CheckingObjectOutputStream - error delegating to writeObject :

Implications of setRecreateBookmarkablePagesAfterExpiry()

Hi all, I have an application where I set cookies with the app's context + mountedPageUrl as the cookie's path. Something like this: 'wicket-sandbox/pageA' Work's fine out of the box. Now I want to have a SessionExpiredPage. According to this https://issues.apache.org/jira/browse/WICKET-4014 I

Re: stop wicket from rewriting references in my css file

Sounds like you have enabled the css compressor / rewriter. By default it is off. This assumes that you are letting wicket handle the css (which you do, as you mention it is a shared resource). You are looking for Application#getResourceSettings() and

Re: stop wicket from rewriting references in my css file

I think you forgot to "mention" the problem itself. It is not clear at all what you are talking about. Some examples would be very helpful! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jun 15, 2016 at 12:18 PM, nino martinez wael <

Re: stop wicket from rewriting references in my css file

I forgot to mention that it's wicket 6.22 On Wed, Jun 15, 2016 at 12:11 PM, nino martinez wael wrote: > Hi > > I currently have an issue where I add a shared css resource, but > wicket rewrites all references in the resource. I can't seem to find > the setting to

stop wicket from rewriting references in my css file

Hi I currently have an issue where I add a shared css resource, but wicket rewrites all references in the resource. I can't seem to find the setting to turn of that part of wickets processing? -- Best regards / Med venlig hilsen Nino Martinez

Re: wicket 1.4.12 https issue - Is it a wicket version compatibility issue with the other software's?

Hi, Wicket 1.4.x and 1.5.x use vanilla JavaScript for the Ajax stuff. Since Wicket 6.x we use jQuery for better browser compatibility. Try with Wicket 6.23.0/7.3.0 if you can! Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Wed, Jun 15, 2016 at 12:36 AM,

Re: wicket-guice and recursive injection of non serializable JPA2 objects

Dieter, Since the data provider is inject as a proxy, only the proxy should be serialized. On deserialization it should look up the actual data provider again. Can you share some code so we can see how you set things up? What you are trying is something that should work out of the box - it does