>From a quick glance (and im not at all familiar with PageableListView - but am alright with their parent - ListView)
Has it anything to do with not calling setReuseItems(true) on the list view itself? - Ie, its destroying the links, then recreating them each request? Rgds Ned Michael Oswell wrote: > > I am running into an issue that I _think_ is related to our terracotta > installation. > > 1. User visits page with a PageableListView. > 2. User navigates to another page in the PageableListView > 3. User clicks on a link generated within the listview > > The following exception is generated > >>> org.apache.wicket.WicketRuntimeException: component >>> mainContentPanel:photoListContainer:photoList:82:switchLink not >>> found on page com.example.wicket.pages.ExamplePage[id = 2], >>> listener interface = [RequestListenerInterface >>> name=IBehaviorListener, method=public abstract void >>> org.apache.wicket.behavior.IBehaviorListener.onRequest()] > > > If I run only one server, then everything works as expected. As soon > as I add extra servers I begin to see this error. > From what I can tell, it appears as though the page map is not being > distributed via terracotta, though I could be wrong. :) > The reason I think this is it appears as though the PageableListView > page that I navigate to doesn't exist in the pagemap on the server > that handles the request when I click a link and as such, generates > the above exception. > > Installation: > Terracotta 2.7.1 > Wicket 1.3.5 > tim-wicket-1.3-1.1.3 > > Any suggestions welcome. > > thanks, > > -- Mike > -- View this message in context: http://www.nabble.com/Terracotta-integration-and-issue-sharing-pagemaps-tp20946423p20947187.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
