Re: PageExpiredException not working on Session expired, wicket 1.5.11.
Hi, Thank's for your answer, Martin Grigorov-4 wrote > Wicket will throw this exception only when you make a request to a page > from this expired session. > It will not throw the exception if there is no request. I am trying to that, there is a request!!, but when i make the request to a page from the expired session the browser can't get the request page (because the session expired) and nothing else happens, there isn't a PageExpiredException, that's the big problem! How can i get a PageExpiredException when i make a request to a page form this expired session? which is the correct way to do that? thank's, excuse me my bad english. I'am from Arg. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/PageExpiredException-not-working-on-Session-expired-wicket-1-5-11-tp4667055p4667060.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
WiQuery: positioning a dialog when reusing it
In my application I am using WiQuery's 'Dialog' for a global page dialog that gets constructed in my page base class. Each time I want to show a dialog I embed a different panel in it and then show it. Usually I would like to display smaller dialogs that fit on the screen using WindowPosition.CENTER while for larger (i.e. longer) dialogs WindowPosition.TOP would be more appropriate. Now I see that setting the window position on the already constructed Dialog object does not have any effect, the only way I can actually set the position is by setting the position after construction, i.e. before the dialog gets rendered for the first time. I actually found this by trial-and-error, and the (rather terse) WiQuery documentation does not give me much more of a hint. Thus asking you - is there a way to reposition a reused dialog? If yes, how? It seems so weird I did not find anything on this because this requirement seems fairly typical to me... Cheers, Martin -- -- mdie...@gmail.com --/-- mar...@the-little-red-haired-girl.org - / http://herbert.the-little-red-haired-girl.org / - - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Problem with FormTester and selection on dropDownChoice
Hello List, just stumbled of this isue and the tip from Sven Maier saved my day. Is this something that should be looked into and perhaps changed in later version? The current behavior is not very intuitive. Bert On 6 January 2014 14:10, Kev wrote: > Yes it works. > Thank you very much. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Problem-with-FormTester-and-selection-on-dropDownChoice-tp4663439p4663495.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: PageExpiredException not working on Session expired, wicket 1.5.11.
Hi, On Thu, Aug 14, 2014 at 5:45 PM, ntvg wrote: > > > I am trying to server a particular error page when session timeouts to my > users. For this i configured the error page on my Application's init > method. > But this thing is not working. > > I set up the session tiemout in 1 minute, after that nothing happen, I went > through the logs, but wicket didn't throw any PageExpiredException. > Wicket will throw this exception only when you make a request to a page from this expired session. It will not throw the exception if there is no request. > > When session timeouts wicket simply logs it as: Session unbound: > C061F4F21C41EDF13C66795DAC9EDD02 Removing data for pages in session with id > 'C061F4F21C41EDF13C66795DAC9EDD02' > This is expected, yes. Wicket notifies the application (and ISessionStore's listeners) when the session is gone. But it is not possible to notify the browser (by showing the SessionExpiredPage) because the client is gone, right! > > this is my init method in my customApplication > > protected void init() { > super.init(); > > > > this.getApplicationSettings().setPageExpiredErrorPage(SessionExpiredPage.class); > > > this.getExceptionSettings().setUnexpectedExceptionDisplay(IExceptionSettings.SHOW_INTERNAL_ERROR_PAGE); > ... > ... > } > > I try with differents IExceptionSettings like SHOW_NO_EXCEPTION_PAGE or > SHOW_EXCEPTION_PAGE > > my SessionExpiredPage.class > > public class SessionExpiredPage extends WebPage { > > public SessionExpiredPage() { > this.setOutputMarkupId(true); > this is strange. the page cannot and need not to have markup id. Wicket will ignore it. > this.add(new Label("title", "SesiĆ³n Expirada")); > CSSLoader.get().appendCssUntil(this, SessionExpiredPage.class); > } > } > > And i have a custom implementation of AbstractRequestCycleListener i > override the OnException method But, when my session expire, I never pass > in > the "onException". > Yes, because the exception is thrown only when the client returns later and try to use an expired page/a page from expired session. > > Thank You, best regards. > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/PageExpiredException-not-working-on-Session-expired-wicket-1-5-11-tp4667055.html > Sent from the Users forum mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >