Hi,
we’ve a very odd problem and are somewhat stuck, maybe someone here on the list
has seen this sort of behaviour before.
We’ve deployed a small wicket app (4 pages) to a tomcat7 server and all 4 pages
work just fine on the live system.
However, when googlebot scrapes the pages, we see
Well, you have the wicket component tree path to what's not found:
titleBar:menu:2:link
The 3rd (index 2) menu link was missing at the point your page was rendered.
Start thinking about how your 'menu' component could miss that from the
mode.
Or perhaps someone used the back-page button and your
ie: How do you create the menu links?
Where does the model come from and are those links dynamic?
On Tue, Sep 16, 2014 at 11:15 AM, Paul Bors p...@bors.ws wrote:
Well, you have the wicket component tree path to what's not found:
titleBar:menu:2:link
The 3rd (index 2) menu link was missing at
