It looks like you have logic that changes addcontactButton's visibility or enable-bility in some conditions. Check what exactly changes when you open page B.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Mar 11, 2016 at 9:25 AM, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > Hi > > I have something strange (as always). Two pages A and B > > If I open the two pages in the same session on two different tabs. > Invoking an ajax behavior (wicket modal panel) yields > > Access Denied > > stack tells me this: > > Behavior rejected interface invocation. Component: [AjaxLink > [Component id = addcontactButton]] Behavior: > org.apache.wicket.ajax.markup.html.AjaxLink$1@79f8700 Listener: > [RequestListenerInterface name=IBehaviorListener, method=public > abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()] > > If I only mess around with page A there are no problems. But opening > Page B in another tab apparently triggers this. It does not matter if > there is ajax or not on page B > > > -- > Best regards / Med venlig hilsen > Nino Martinez > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
