Re: Problem migrating to Wicket 7

2016-06-26 Thread Dirk Forchel
Ciao Andrea, it works! Great! I'll wait until the official release of Wicket 7.4 Dirk -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674963.html Sent from the Users forum mailing list archive at Nabble.com

Re: Problem migrating to Wicket 7

2016-06-23 Thread Andrea Del Bene
n context: http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674910.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org

Re: Problem migrating to Wicket 7

2016-06-18 Thread Martin Grigorov
e reason could be the fact, that we use two nested Border >>> components. >>> But the behavior should work with this combination as well, I think. >>> Could you please have a look at this problem. >>> >>> Here is the quickstart: myprojec

Re: Problem migrating to Wicket 7

2016-06-17 Thread Martin Grigorov
. >> But the behavior should work with this combination as well, I think. >> Could you please have a look at this problem. >> >> Here is the quickstart: myproject2.zip >> <http://apache-w

Re: Problem migrating to Wicket 7

2016-06-17 Thread Martin Grigorov
apache-wicket.1842946.n4.nabble.com/file/n4674910/myproject2.zip> > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674910.html > Sent from the Users forum mailing list archive at Nabble.com. > >

Re: Problem migrating to Wicket 7

2016-06-16 Thread Dirk Forchel
.com/file/n4674910/myproject2.zip> -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674910.html Sent from the Users forum mailing list archive at Nabble.com. ---

Re: Problem migrating to Wicket 7

2016-06-08 Thread Dirk Forchel
6 but NOT with Wicket 7. I was able to figure out, that the ChildFirstHeaderRenderStrategy#renderChildHeaders method never calls component.internalRenderHead(headerContainer) and I'm wondering why!? This might be due to some changes made under the hood of Wicket 7. -- View this message in context: http://apache-wicket.1

Re: Problem migrating to Wicket 7

2016-06-08 Thread Martin Grigorov
he-wicket.1842946.n4.nabble.com/file/n4674857/myproject.zip> >> >> PS: By the way, I meant the attachment at my previous post. >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Problem-

Re: Problem migrating to Wicket 7

2016-06-08 Thread Martin Grigorov
ssage in context: > http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674857.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: user

Re: Problem migrating to Wicket 7

2016-06-08 Thread Dirk Forchel
Nabble does. Here it is again ... myproject.zip <http://apache-wicket.1842946.n4.nabble.com/file/n4674857/myproject.zip> PS: By the way, I meant the attachment at my previous post. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wi

Re: Problem migrating to Wicket 7

2016-06-08 Thread Martin Grigorov
Components. > I guess, that the problem are the two nested Border components. But I don't > feel confident. As stated above, I've attached a quickstart application > inorder to reproduce the problem. > > -- > View this message in context: > http://apache-wicket.1842946.

Re: Problem migrating to Wicket 7

2016-06-07 Thread Dirk Forchel
inorder to reproduce the problem. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Problem-migrating-to-Wicket-7-tp4674842p4674846.html Sent from the Users forum mailing list archive at Nabble.com

Problem migrating to Wicket 7

2016-06-05 Thread Dirk Forchel
Hello Martin, after migrating our Wicket application from Wicket 6.22 to Wicket 7.3, we've noticed, that some Behavior's renderHead method is not called anymore. Which means, HeaderItems added to the Response object for rendering ResourceReferences and OnDomReady JavaScripts statements are