:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664807.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
but set the page title. I've checked my
authorization strategy and I don't see anything problematic.
No doubt it will be something silly but at the moment I'm perplexed.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664807
submit.
I'll submit the quickstart but I still find it hard to believe it's a bug.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774p4664820.html
Sent from the Users forum mailing list archive at Nabble.com
this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
expires. This is something we want to avoid.
We're using Wicket 6.14. Any thoughts?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Page-Expiration-tp4664774.html
Sent from the Users forum mailing list archive at Nabble.com
Hi,
On Wed, Oct 17, 2012 at 7:24 AM, Ondrej Zizka ozi...@redhat.com wrote:
You were right, like usually :)
What's the preffered way for CDI fields - making them transient, or the
class serializable?
CDI injects serializable proxy instead of your bean, so there is no
reason to make it
You were right, like usually :)
What's the preffered way for CDI fields - making them transient, or the
class serializable?
Thanks,
Ondra
On Tue, 2012-10-09 at 15:52 +0200, Ondrej Zizka wrote:
I was thinking about that, but saw no errors in the log. Maybe hidden?
What would be the logging
I was thinking about that, but saw no errors in the log. Maybe hidden?
What would be the logging group?
Thanks,
Ondra
On Tue, 2012-10-09 at 07:41 +0300, Martin Grigorov wrote:
Hi,
Check your logs for errors related to the serialization of the page.
If the page is not properly serialized
by looking for a JS onClick event/behavior through your recent
changes :)
Or add some code for us to view...
~ Thank you,
Paul Bors
-Original Message-
From: Ondrej Zizka [mailto:ozi...@redhat.com]
Sent: Monday, October 08, 2012 9:37 PM
To: wicket-users
Subject: Page
Hi,
I have an AjaxEditableLabel wrapped in a component.
After some changes (I'm still finding which), it's behavior gone totally
astray:
On click, it gave me Page Expired every time.
That was happening with
this.getPageSettings().setRecreateMountedPagesAfterExpiry(false);
When this is
Start by looking for a JS onClick event/behavior through your recent changes
:)
Or add some code for us to view...
~ Thank you,
Paul Bors
-Original Message-
From: Ondrej Zizka [mailto:ozi...@redhat.com]
Sent: Monday, October 08, 2012 9:37 PM
To: wicket-users
Subject: Page expiration
Hi,
Check your logs for errors related to the serialization of the page.
If the page is not properly serialized then next attempts to find it
will fail with PageExpiredException.
On Tue, Oct 9, 2012 at 4:37 AM, Ondrej Zizka ozi...@redhat.com wrote:
Hi,
I have an AjaxEditableLabel wrapped in a
Hi all,
The web app I've been working on has some issues with the back button. For
instance, when using DefaultDataView, if a user goes back a page after
clicking a column heading, and then clicks a different link on the page, it
would cause an error. This problem was easily solved manually by
Ok... Our page had a StatelessForm inside. We changed it to just Form.
When the form was submitted, we had a bookmarkable page as a response
page and now we changed the call to produce a non-bookmarkable page.
This is:
onSubmit() {
...
//setResponsePage(MyResponsePage.class); // - REMOVED
1) Why setting bookmarkable or not bookmarkable response page makes the
difference between expiring and not expiring the current page?
Basically, the page instances are versioned to framework be able to get them
back. The default versioning implementation encode page version information
at url. As
1) So, what does the fact that it creates a new pagemap (or not) has to
do with the current page been expired or not? I mean, I understand the
URL encode for the page versioning stuff, but I don't get why the page
is not expired. Maybe because when I hit the back button, the URL points
to the
Thank you for your time.
Now we know that all of our pages must be stateless AND we need it to
expire them anyway. Maybe Wicket is not prepared for this so we'll try
it manually.
Pedro Santos escribió:
1) The browser keep the page url on his history. If that url don't has
any historical
Hi, I have another question...
in Wicket (1.4.2), can I force the expiration of a page?
Specifically, if users hit browser's back-button, I'd like to show them
the page-expired message.
I've already tried to invalidate the session, but I got a horrible
exception when re-submitting the form
The page returned from back button came from pagemap. Make sure to remove it
from there and you get the expired exception.
On Tue, Oct 27, 2009 at 11:57 AM, Tomás Rossi tro...@mecon.gov.ar wrote:
Hi, I have another question...
in Wicket (1.4.2), can I force the expiration of a page?
Nothing seems to work.
Does the fact that the page I want to expire is the home page has
anything to do with it?
Pedro Santos escribió:
The page returned from back button came from pagemap. Make sure to remove it
from there and you get the expired exception.
On Tue, Oct 27, 2009 at 11:57
You are aware that to an page expire, it has to be statefull, right?
In a statefull page:
getPage().getPageMap().clear()
and the previous versions will to be removed from pagemap, then you got the
page expired when try to back to then...
On Tue, Oct 27, 2009 at 4:05 PM, Tomás Rossi
.
Thanks a lot.
Cheers.
--
View this message in context:
http://www.nabble.com/page-expiration-of-main-application-when-using-iframe-tp22367009p22367009.html
Sent from the Wicket - User mailing list archive at Nabble.com
Hi!
I would like to ignore page expired on certain pages. What I mean is
that in general it is ok to follow the instruction:
getApplicationSettings().setPageExpiredErrorPage(LoginPage.class);
However, on certain pages where the session is not so important, I
would like to redirect back to the
when you hit pageexpired exception you do not know which page caused it
-igor
On Fri, Jan 16, 2009 at 11:18 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Hi!
I would like to ignore page expired on certain pages. What I mean is
that in general it is ok to follow the
when you hit pageexpired exception you do not know which page caused it
Is it possible that there could be some query parameters that could be
used to deduce such information?
**
Martin
On Fri, Jan 16, 2009 at 11:18 AM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Hi!
I would
Specifically, if it is a Mounted Bookmarkable page, the page name
should be available in the url?
**
Martin
2009/1/16 Martin Makundi martin.maku...@koodaripalvelut.com:
when you hit pageexpired exception you do not know which page caused it
Is it possible that there could be some query
bookmarkable urls do not generate a page expired error, the urls that
do generally look like this:
?wicket:interface=2:ff.sdfsdf.sdf:ILinkListener
where the only information you have about the page is 2.
you can write your own coding strategy that always appends the class
name of the last
to process the hidden field in case of page
expiration? AbstractRequestCycleProcessor?
**
Martin
2009/1/16 Igor Vaynberg igor.vaynb...@gmail.com:
bookmarkable urls do not generate a page expired error, the urls that
do generally look like this:
?wicket:interface=2:ff.sdfsdf.sdf:ILinkListener
where
Hi everyone,
tensions/markup/html/datepicker/style/aqua/menuarrow.gif
Could this be the cause of the problem?
Thx,
Dariusz
-Original Message-
From: Dipu Seminlal [mailto:[EMAIL PROTECTED]
Sent: 20 September 2007 13:03
To: users@wicket.apache.org
Subject: Re: Page expiration
Hi
Hi,
I've came across a strange behaviour. I'm running Wicket app on Jetty
server and most of the times it's working fine but from time to time I'm
getting Page expired message even if user is actively using the app.
Unfortunately it's not happening on the same events. Sometimes it's
after
Hi,
Can you please check if you have any img tags in your html with empty src
attributes ?
Regards
Dipu
On 9/20/07, Holda, Dariusz [EMAIL PROTECTED] wrote:
Hi,
I've came across a strange behaviour. I'm running Wicket app on Jetty
server and most of the times it's working fine but from time
@wicket.apache.org
Subject: Re: Page expiration
Hi,
Can you please check if you have any img tags in your html with empty
src
attributes ?
Regards
Dipu
On 9/20/07, Holda, Dariusz [EMAIL PROTECTED] wrote:
Hi,
I've came across a strange behaviour. I'm running Wicket app on Jetty
server and most
September 2007 13:03
To: users@wicket.apache.org
Subject: Re: Page expiration
Hi,
Can you please check if you have any img tags in your html with empty
src
attributes ?
Regards
Dipu
On 9/20/07, Holda, Dariusz [EMAIL PROTECTED] wrote:
Hi,
I've came across a strange behaviour. I'm
wicket snapshot from July 30.
shumbola
Of course, it is wicket-1.3 snapshot ;)
--
View this message in context:
http://www.nabble.com/Page-expiration-tf4191798.html#a11959367
Sent from the Wicket - User mailing list archive at Nabble.com
35 matches
Mail list logo