You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Tom Eicher <ro...@teicher.net> on 2015/08/13 17:39:01 UTC
Link not working after upgrade from 6.8.0 to 6.20.0
Hello,
I was thinking, I'd just upgrade to 6.latest before
planning the big move to Wicket 7, but I experience
some very strange behaviour:
All throughout my app. I am using Links like this:
Link<Void> l = new Link<Void>("NavBarAppLink") {
@Override
public void onClick() {
setResponsePage(page);
}
};
l.setBody(Model.of(someText));
return l;
In Wicket 6.8.0 this produced like:
<a
href="../page?4-1.ILinkListener-PortalBody-PortalNavBar-NavBarItems-2-NavBarItem-NavBarAppItem-NavBarItems-0-NavBarItem-NavBarAppItem-NavBarAppLink"
wicketpath="PortalBody_PortalNavBar_NavBarItems_2_NavBarItem_NavBarAppItem_NavBarItems_0_NavBarItem_NavBarAppItem_NavBarAppLink">TheApp</a>
and the click works.
In Wicket 6.20.0 this just produces
<a href="./Home"
wicketpath="PortalBody_PortalNavBar_NavBarItems_1_NavBarItem_NavBarAppItem_NavBarAppLink">TheApp</a></li>
Where "Home" ist the mount path of the current page, not the intended
target. So basically all links just go to themselves.
I have no idea what could be causing this.
Just changing the wicket project libraries makes the app work again.
-rw-r--r-- 1 teicher staff 35284 30 Jul 16:31 wicket-cdi-6.20.0.jar
-rw-r--r-- 1 teicher staff 35496 30 Jul 17:20 wicket-cdi-6.8.0.jar
-rw-r--r-- 1 teicher staff 2115670 30 Jul 16:31 wicket-core-6.20.0.jar
-rw-r--r-- 1 teicher staff 1910550 30 Jul 17:20 wicket-core-6.8.0.jar
-rw-r--r-- 1 teicher staff 113012 30 Jul 16:31
wicket-devutils-6.20.0.jar
-rw-r--r-- 1 teicher staff 113231 30 Jul 17:20 wicket-devutils-6.8.0.jar
-rw-r--r-- 1 teicher staff 1381884 30 Jul 16:31
wicket-extensions-6.20.0.jar
-rw-r--r-- 1 teicher staff 1371703 30 Jul 17:20
wicket-extensions-6.8.0.jar
-rw-r--r-- 1 teicher staff 86597 30 Jul 16:32 wicket-request-6.20.0.jar
-rw-r--r-- 1 teicher staff 86496 30 Jul 17:20 wicket-request-6.8.0.jar
-rw-r--r-- 1 teicher staff 426848 30 Jul 16:32 wicket-util-6.20.0.jar
-rw-r--r-- 1 teicher staff 415481 30 Jul 17:20 wicket-util-6.8.0.jar
Any hints appreciated.
Thanks, Tom.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Link not working after upgrade from 6.8.0 to 6.20.0
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
Do you use WicketStuff-Portlet ? I see some "Portal"s in the paths.
Try to upgrade version by version and see at which one exactly it starts to
fail.
If there are no portlets involved then please create a quickstart app and
attach it to JIRA so we can debug it. Thanks!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Aug 13, 2015 at 6:39 PM, Tom Eicher <ro...@teicher.net> wrote:
> Hello,
>
> I was thinking, I'd just upgrade to 6.latest before
> planning the big move to Wicket 7, but I experience
> some very strange behaviour:
>
> All throughout my app. I am using Links like this:
>
> Link<Void> l = new Link<Void>("NavBarAppLink") {
> @Override
> public void onClick() {
> setResponsePage(page);
> }
> };
> l.setBody(Model.of(someText));
> return l;
>
> In Wicket 6.8.0 this produced like:
>
> <a
> href="../page?4-1.ILinkListener-PortalBody-PortalNavBar-NavBarItems-2-NavBarItem-NavBarAppItem-NavBarItems-0-NavBarItem-NavBarAppItem-NavBarAppLink"
> wicketpath="PortalBody_PortalNavBar_NavBarItems_2_NavBarItem_NavBarAppItem_NavBarItems_0_NavBarItem_NavBarAppItem_NavBarAppLink">TheApp</a>
>
> and the click works.
>
> In Wicket 6.20.0 this just produces
>
> <a href="./Home"
> wicketpath="PortalBody_PortalNavBar_NavBarItems_1_NavBarItem_NavBarAppItem_NavBarAppLink">TheApp</a></li>
>
> Where "Home" ist the mount path of the current page, not the intended
> target. So basically all links just go to themselves.
>
> I have no idea what could be causing this.
> Just changing the wicket project libraries makes the app work again.
>
> -rw-r--r-- 1 teicher staff 35284 30 Jul 16:31 wicket-cdi-6.20.0.jar
> -rw-r--r-- 1 teicher staff 35496 30 Jul 17:20 wicket-cdi-6.8.0.jar
> -rw-r--r-- 1 teicher staff 2115670 30 Jul 16:31 wicket-core-6.20.0.jar
> -rw-r--r-- 1 teicher staff 1910550 30 Jul 17:20 wicket-core-6.8.0.jar
> -rw-r--r-- 1 teicher staff 113012 30 Jul 16:31
> wicket-devutils-6.20.0.jar
> -rw-r--r-- 1 teicher staff 113231 30 Jul 17:20
> wicket-devutils-6.8.0.jar
> -rw-r--r-- 1 teicher staff 1381884 30 Jul 16:31
> wicket-extensions-6.20.0.jar
> -rw-r--r-- 1 teicher staff 1371703 30 Jul 17:20
> wicket-extensions-6.8.0.jar
> -rw-r--r-- 1 teicher staff 86597 30 Jul 16:32
> wicket-request-6.20.0.jar
> -rw-r--r-- 1 teicher staff 86496 30 Jul 17:20 wicket-request-6.8.0.jar
> -rw-r--r-- 1 teicher staff 426848 30 Jul 16:32 wicket-util-6.20.0.jar
> -rw-r--r-- 1 teicher staff 415481 30 Jul 17:20 wicket-util-6.8.0.jar
>
> Any hints appreciated.
>
> Thanks, Tom.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>