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
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
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
.
>> 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
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.
>
>
.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.
---
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
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-
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
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
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.
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
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
13 matches
Mail list logo