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 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 page was not in the > page store? > > On Tue, Sep 16, 2014 at 3:42 AM, Robert Gründler <rob...@dubture.com> > wrote: > >> 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 ComponentNotFound >> exceptions: >> >> ComponentNotFoundException: Could not find component >> 'titleBar:menu:2:link' on page XYZ >> >> We’ve tried to fetch the page as google bot from the webmaster tools, but >> the exception is not being triggered either. >> >> No matter how we request the page, we cannot reproduce this exception. >> Only 2 or 3 times a day when the bot >> indexes us, we see this in the logs. >> >> We’ve also made sure the pages are stateless using the @StalessComponent >> annotation in combination with the StatelessChecker listener. >> >> Has anyone an idea what could cause this? >> >> thanks! >> >> >> -robert >> >> >> >> >
