As a follow up:
Is there a way to test the back-button (without firing up jetty and
resorting to selenium / htmlunit)?
btw: I know WicketTester has trimmed-down versions of certain components
(MockApplication(), MockPageManager etc). Maybe there is an implementation
that keeps track of the pages
Hi Rob,
you're absolutely right: The issue's title should have been changed.
I've missed the opportunity when I found the real error :(.
Something to keep in mind for future changes!
Sven
Am 10. Oktober 2017 13:47:53 MESZ schrieb Rob Audenaerde
:
>Hi Sven,
>
>Thanks for your reply!
>
>I was mis
Hi Sven,
Thanks for your reply!
I was mistaken in believing 7.8.0 was still broken (perhaps not cleaned-up
enough) and can confirm 7.8.0 fixes the issue.
After reading it seems the title of the issue is slightly misleading (as
you commented: This doesn't have anything to do with ModalWindow - ev
That's WICKET-6387 probably.
Regards
Sven
Am 10. Oktober 2017 12:04:33 MESZ schrieb Rob Audenaerde
:
>Hi all,
>
>We upgraded some time ago from Wicket 7.6.0 to Wicket 7.7.0 and now we
>see
>that that back-button behaves differently?
>Before, pressing back would return the page with all the ajax
Hi,
How do you load the model ?
If you use dynamic model, like LoadableDetachableModel, then each render of
the page will load its current state from the DB.
By default org.apache.wicket.markup.html.WebPage#setHeaders() disables the
caching so there shouldn't be such problem.
Martin Grigorov
Wick
Hi,
I am not sure that I understand you correctly but I think you can use
PageReference for this.
When moving from first page to the second page pass page.getPageReference()
to the second.
When the form in the second is submitted just do:
setResponsePage(pageReference.getPage())
This will return
Hi Arthur,
no worries. This was just a hint. Wireshark might look quite discouraging at
first sight.
When it is started it will show all the network traffic on the machine, but
that output can be filtered quite effectively.
If it is really important, then wireshark can analyse gigabyte big tcp
Hi Martin,
I had a quick read through it and this is not an option. I can't
reproduce the error and it is not given when it will reoccur. If I
understood it correctly I'd have to caputre all network traffic for my
application until the point the error occurs to be able to use wireshark
and an
Hi,
have you thought about wireshark?
Easy to set up and not all that hard to handle. Filters are powerful and most
interestingly for Web-Development
ist the "Follow TCP stream" function.
http://www.wireshark.org/docs/wsug_html_chunked/ChAdvFollowTCPSection.html
mf
Am 06.11.2013 um 15:27 schr
Hi,
I would expect it to hit the container. Debuggin and testing on a test
environment works and hits it. Unfortunatelly there is no way to
definitely proove that the error in question hits it to. I do know that
the onConfigure is not hit. I don't have access to the access logs.
Is there a w
Hi,
It looks like the page is loaded from the browser/proxy cache.
Can you verify that the web container is hit ? E.g. check its access logs
On Tue, Nov 5, 2013 at 4:05 PM, Artur Kronenberg <
artur.kronenb...@openmarket.com> wrote:
> Hi,
>
> I have a rather odd problem with a page of mine. The
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Tuesday, September 04, 2012 12:49 PM
To: users@wicket.apache.org
Subject: Re: Back button doesn't work with AjaxTabbedPanel
So, my conclusion from this discussion is that TabbedPanel should be used
instead of AjaxTabbedPanel if browse
uest/mapper/parame
> ter/PageParameters.html
>
> Not sure if you really want to go to this extreme, but feel free to do so if
> you must.
>
> ~ Thank you,
> Paul Bors
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Saturday, Se
cket.apache.org
Subject: Re: Back button doesn't work with AjaxTabbedPanel
How do I know when the back button is pressed?
On Fri, Aug 31, 2012 at 6:48 PM, Paul Bors wrote:
> Can't you just keep a reference to the backPage and then simply call
> setResponsePage(backPage)?
From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Friday, August 31, 2012 7:07 PM
> To: users@wicket.apache.org
> Subject: Re: Back button doesn't work with AjaxTabbedPanel
>
> So, is there an easy way to support Back button with AjaxTabbedPanel?
>
> On Thu, Aug 30, 2012 a
Can't you just keep a reference to the backPage and then simply call
setResponsePage(backPage)?
~ Thank you,
Paul Bors
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Friday, August 31, 2012 7:07 PM
To: users@wicket.apache.org
Subject: Re: Back button doesn&#
So, is there an easy way to support Back button with AjaxTabbedPanel?
On Thu, Aug 30, 2012 at 1:04 PM, Alec Swan wrote:
> Well, I have other ajax interactions and I thought if I could fix Back
> button for AjaxTabbedPanel I'd be able to fix it for other ajax
> interactions.
>
> On Thu, Aug 30, 20
Well, I have other ajax interactions and I thought if I could fix Back
button for AjaxTabbedPanel I'd be able to fix it for other ajax
interactions.
On Thu, Aug 30, 2012 at 12:51 PM, Sven Meier wrote:
> Silly question: Why don't you use a non-Ajax Tabbedpanel?
>
> Sven
>
>
> On 08/30/2012 08:45 P
Silly question: Why don't you use a non-Ajax Tabbedpanel?
Sven
On 08/30/2012 08:45 PM, Alec Swan wrote:
What can I do to allow user to go back to the previously selected tab
with a Back button? I tried the following approach but it doesn't seem
to work:
http://grepcode.com/file/repo1.maven.org
What can I do to allow user to go back to the previously selected tab
with a Back button? I tried the following approach but it doesn't seem
to work:
http://grepcode.com/file/repo1.maven.org/maven2/org.wicketstuff/jquery-examples/1.4.7/org/wicketstuff/jquery/ajaxbackbutton/Page4AjaxBackButton.java
Swapping components via Ajax will not change the browser's page history.
Thus the Back button works as expected - it takes you to the previous url.
Sven
On 08/30/2012 07:55 PM, Alec Swan wrote:
Hello,
I am using AjaxTabbedPanel to implement an ajax-swappable menu on the
Main page which is moun
; http://apache-wicket.1842946.n4.nabble.com/Re-Back-button-is-troubling-session-management-tp4649801p4649805.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-un
I used the same logic in onBeforeRender and it is working...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Back-button-is-troubling-session-management-tp4649801p4649805.html
Sent from the Users forum mailing list archive at Nabble.com
ect myObject) {
this.myObject = myObject;
}
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Re-Back-button-is-troubling-session-management-tp4649801p4649804.html
Sent from the Users forum mailing list archive
Hi,
where did you pu the logic to check if user has already signed in
(onInitialize, onBeforeRender, etc...)? Could you show your code?
Hi,
After I log in that application, I am not suppose to see login page of the
app when I press back button. Though I am not able to go to login url as I
am c
1. use LDM or AbstractReadOnlyModel to load your data on PageA. i use LDMs
to load almost all data and about the only time I don't use an LDM is during
a wizard scenario, where the same object needs to be updated across request.
2. disable caching of the page so that the server is requested whe
, December 8, 2011 7:31 PM
Subject: Re: Back button not work in Wicket 1.5.3 when component structure is
not changed
Actually the important method is modelChanging(). It calls #dirty() for you.
In the code below there is no change in the state managed by Wicket (a
change in a model with setDefaultModel
Actually the important method is modelChanging(). It calls #dirty() for you.
In the code below there is no change in the state managed by Wicket (a
change in a model with setDefaultModel[Object]()) and that's the
reason the request doesn't trigger new page version.
On Thu, Dec 8, 2011 at 12:27 PM,
modelChanged()?
Sent from tablet device. Please excuse typos and brevity.
On Dec 8, 2011 12:58 AM, "Dan Retzlaff" wrote:
> Hi, Robin. I am not a core developer, but I believe this is as designed. If
> you want the page version to be incremented, you can call Page#dirty() in
> your onClick(). Ot
Hi Dan,
Thanks for the quick response. The dirty() method does make the back button
work again.
Regards
Robin
From: Dan Retzlaff
To: users@wicket.apache.org; Robin Shine
Sent: Thursday, December 8, 2011 1:57 PM
Subject: Re: Back button not work in
Hi, Robin. I am not a core developer, but I believe this is as designed. If
you want the page version to be incremented, you can call Page#dirty() in
your onClick(). Otherwise the page version only advances when the component
hierarchy changes or when a component's model changes.
On Wed, Dec 7, 20
martin-g : heh yeah i realized it after hitting on submit but then i thought
he will figure it out ,thanks :)
-
vineet semwal
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Back-button-problem-in-wicket-tp3480260p3483658.html
Sent from the Users forum mailing list
On Fri, Apr 29, 2011 at 12:31 PM, vineet semwal
wrote:
> use spring bean
@vineet: Better use '@SpringBean' because it is not very clear what you mean ;-)
@madaan18: show us some code so we can tell you for sure what the problem is
>
> On Fri, Apr 29, 2011 at 2:55 PM, madaan18 wrote:
>> Hi,
>>
use spring bean
On Fri, Apr 29, 2011 at 2:55 PM, madaan18 wrote:
> Hi,
> Thanks for the help... problem is solved..
> i integrated spring and wicket.. but a new problem has come..
>
> it is saying me to serialize the service class although it is not affecting
> the problem of back button if i don
Hi,
Thanks for the help... problem is solved..
i integrated spring and wicket.. but a new problem has come..
it is saying me to serialize the service class although it is not affecting
the problem of back button if i don't serialize but still throwing an
exception..
I don't wanna serialize my ser
Hi,
It sounds like you use spring dependency injection directly, which will
indeed cause serialization issues. Instead, use the wicket spring
integration, which will inject serializable proxies.
See https://cwiki.apache.org/WICKET/spring.html for more info.
Bas
Op 28-4-2011 8:36, schreef mad
Hi,
what does your application/web server's log say? You should check it for
some Wicket message or exception that could explain page expiration.
Hey,
I am new to wicket.. I was having problem of back button in wicket.. but it
got solved when i made all the pages and service class serializab
Hi,
On Fri, Oct 22, 2010 at 12:53 PM, drf wrote:
>
> I have encountered the following serious issue:
>
> My application consists of one WebPage which has an AjaxTabbedPanel. Each
> tab has an associated panel which includes several menu items (links) which
> can be selected. This works well.
> Ho
Check wicketstuff's jquery project for HistoryAjaxBehavior. May be it helps.
drf wrote:
>
> I have encountered the following serious issue:
>
> My application consists of one WebPage which has an AjaxTabbedPanel. Each
> tab has an associated panel which includes several menu items (links)
> wh
Wicket does not support back button for Ajax application out of the box.
Search in Google/Nabble for suggestions how to make it working for your
application.
On Fri, Oct 22, 2010 at 12:53 PM, drf wrote:
>
> I have encountered the following serious issue:
>
> My application consists of one WebPag
Yes, it does...
Best,
Martin
-Original Message-
From: Steve Swinsburg [mailto:steve.swinsb...@gmail.com]
Sent: Monday, April 26, 2010 3:19 PM
To: users@wicket.apache.org
Subject: Re: Back button
Looks like an issue with Firefox only though, as per the JIRA [1]. If you
follow the
Looks like an issue with Firefox only though, as per the JIRA [1]. If you
follow the recommendation in the JIRA, does that fix the problem?
cheers,
Steve
[1] https://issues.apache.org/jira/browse/WICKET-923
On 26/04/2010, at 5:56 PM, Pointbreak wrote:
> That browser cache issue is what I sugg
That browser cache issue is what I suggested as the culprit earlier on
in this thread, for which Igor replied:
> that doesnt matter because the url of the link you click contains the
> version number of the page
Apparently it does matter? Or am I missing something?
On Mon, 26 Apr 2010 10:21 +03
I found the solution > https://issues.apache.org/jira/browse/WICKET-923
Best,
Martin
-Original Message-
From: Martin Asenov [mailto:mase...@velti.com]
Sent: Monday, April 26, 2010 9:36 AM
To: users@wicket.apache.org
Subject: RE: Back button
Hello, everyone!
I was off during
oesn't occur in IE8.
Best,
Martin
-Original Message-
From: Douglas Ferguson [mailto:doug...@douglasferguson.us]
Sent: Monday, April 26, 2010 9:26 AM
To: users@wicket.apache.org
Subject: Re: Back button
So does this mean that if you won't true BackButtom support you should swall
So does this mean that if you won't true BackButtom support you should swallow
all exceptions.
That doesn't seem right..
D/
On Apr 25, 2010, at 11:26 AM, James Carman wrote:
> I meant "page store", not "session store."
>
> On Sun, Apr 25, 2010 at 12:26 PM, James Carman
> wrote:
>> It would a
I meant "page store", not "session store."
On Sun, Apr 25, 2010 at 12:26 PM, James Carman
wrote:
> It would affect the back button because when Wicket tries to go get
> the specific version of the page back from the session store (only the
> "current" version is kept in the session and the earlie
It would affect the back button because when Wicket tries to go get
the specific version of the page back from the session store (only the
"current" version is kept in the session and the earlier ones are in
the store), it won't be able to find it.
On Sun, Apr 25, 2010 at 11:45 AM, Douglas Ferguso
No.. this is not a serialization issue, unless Igor is correct in that fact
that the exception prevents serialization. But how would that effect the back
button,
should the page on the back button have already been serialized?
Say if I get a hibernate "failed to lazy load" exception, then I hit
That means one of your fields might *not* be Serializable. The error
message usually tells you the exact field that caused the problem (in
development mode).
On Sun, Apr 25, 2010 at 8:26 AM, Nico Guba wrote:
> Hmmm, does that imply that one of the member variables may be Serializable?
>
> On 25
Hmmm, does that imply that one of the member variables may be Serializable?
On 25 Apr 2010, at 05:18, Igor Vaynberg wrote:
> the exception might have caused your page to not be serialized
> properly into the pagestore
>
> -igor
>
> On Sat, Apr 24, 2010 at 6:06 PM, Douglas Ferguson
> wrote:
>>
the exception might have caused your page to not be serialized
properly into the pagestore
-igor
On Sat, Apr 24, 2010 at 6:06 PM, Douglas Ferguson
wrote:
> I just saw the issue again, but this time it happened right after an
> exception. I got an except. Hit back and then it complained that the
I just saw the issue again, but this time it happened right after an exception.
I got an except. Hit back and then it complained that the link didn't exist.
D?
On Apr 24, 2010, at 6:58 PM, Douglas Ferguson wrote:
> Ah yes..
>
> I am definitely seeing the "component not found on page" error.
>
Ah yes..
I am definitely seeing the "component not found on page" error.
Any tips on how to get a quick start for this? Anybody got any example
quickstarts that deal with back button issues?
D/
On Apr 24, 2010, at 6:41 PM, Igor Vaynberg wrote:
> then you would get a page-expired error
>
> -
then you would get a page-expired error
-igor
On Sat, Apr 24, 2010 at 3:34 PM, Douglas Ferguson
wrote:
> Well something is happening, because I see it in the production logs and from
> time to time on my dev machine.
>
> What if the server is restarted?
>
> D/
>
> On Apr 24, 2010, at 11:09 AM,
Well something is happening, because I see it in the production logs and from
time to time on my dev machine.
What if the server is restarted?
D/
On Apr 24, 2010, at 11:09 AM, Igor Vaynberg wrote:
> that doesnt matter because the url of the link you click contains the
> version number of the p
that doesnt matter because the url of the link you click contains the
version number of the page
-igor
On Sat, Apr 24, 2010 at 2:35 AM, Pointbreak
wrote:
> In firefox it doesn't. Firefox reads the page back from it's in memory
> cache, which is the state before you clicked the ajax link. The hea
In firefox it doesn't. Firefox reads the page back from it's in memory
cache, which is the state before you clicked the ajax link. The headers
should be changed to force firefox to request the page from the server
(wicket). There are other threads on this subject, and frankly I do not
understand wh
the back button should roll the page back to the state that contained the item
-igor
On Fri, Apr 23, 2010 at 9:28 PM, Douglas Ferguson
wrote:
> Could this possibly happen if the following occurred.
>
> 1) Load a page with a repeater on it
> 2) Click on an ajax link that would remove an item from
Could this possibly happen if the following occurred.
1) Load a page with a repeater on it
2) Click on an ajax link that would remove an item from the repeater
3) Click the back button. Click on the link for the item you removed.
D/
On Apr 23, 2010, at 10:32 AM, Martin Asenov wrote:
> Would so
I see this alot in my production logs as well. I thought that it was just a
"gotcha" with wicket.
Please let me know if you are unable to get a quick start and I'll see what I
can do.
D/
On Apr 23, 2010, at 11:09 AM, Igor Vaynberg wrote:
> reproduce it in a quickstart and attach it to a jira
reproduce it in a quickstart and attach it to a jira issue
-igor
On Fri, Apr 23, 2010 at 8:32 AM, Martin Asenov wrote:
> Would someone assist me on this?
>
> Thank you in advance!
>
> -Original Message-
> From: Martin Asenov [mailto:mase...@velti.com]
> Sent: Friday, April 23, 2010 9:38
Would someone assist me on this?
Thank you in advance!
-Original Message-
From: Martin Asenov [mailto:mase...@velti.com]
Sent: Friday, April 23, 2010 9:38 AM
To: users@wicket.apache.org
Subject: Back button
Hello, everyone!
I've got a page with a repeater with cells - every single cell
use setResponsePage() to go to the next page when everything is a-ok.
Wicket will instruct the browser to redirect to the new page (iirc).
Martijn
On Wed, Apr 21, 2010 at 11:58 PM, Brian Laframboise
wrote:
> Thanks Edward. I was hoping for some means of doing this in a
> redirect-after-post kind
Thanks Edward. I was hoping for some means of doing this in a
redirect-after-post kind of way so that the javascript response to the
client actually caused the browser to request the next wizard page via a new
url, creating a back-button history entry. I guess generating that URL for a
non-bookmark
Since you are changing the DOM dynamically using Ajax, the browser --
correctly I would say -- isn't considering this a page change, so the
back button should take you back to the page prior to the wizard.
The browser history will be immutable from JavaScript, so that's not an option.
To achieve
I need help on implementing listener for browsers back or forward button ,
is it possible to implement ?
fachhoch wrote:
>
> I want to disable back and forward button for which I followed
> HistoryAjaxBehavior example
>
>
> final AjaxLink linkTwo = new AjaxLink("linkTwo") {
>
>
Use a loadable detachable model instead (see also wicket in action,
chapter re models). and in page.ondetach() detach those models.
Martijn
On Thu, Apr 2, 2009 at 1:27 PM, Steve Swinsburg
wrote:
> Thanks Martijn,
>
> Understand re logger and making it a static instance, but what about other
> tr
Thanks Martijn,
Understand re logger and making it a static instance, but what about
other transient fields, is it ok to override getObject on each page an
re setup my transient fields or is this going to cause issues down the
track?
cheers,
Steve
On 2 Apr 2009, at 12:22, Martijn Da
magic word for loggers: static
and your assumption is correct: if you don't do anything, you'll get
NPE's when you reference a transient field on an object that has been
deserialized.
Martijn
On Thu, Apr 2, 2009 at 1:17 PM, Steve Swinsburg
wrote:
> All,
> I have some questions regarding deseria
There are three objects on the page which have injected properties.
The first is an abstract superclass of all pages in the project, I have
checked on other pages and there is no issue with the back button here so I
don't think its the issue but here's the code.
public class AbstractMain extend
Don't send the code for your DAO, send the code where you declare the DAO as
a property of a model or component. Also - do you anywhere in that
component manually assign the DAO by accident?
For example:
MyComponent extends WebMarkupContainer {
@Inject
private CategoryDAO mCategoryDao;
}
On W
Right, sorry its been a while, I had some horrible issues getting tomcat
working properly but I've managed to deploy the project on Tomcat. My
logging setup isn't working perfectly but I'm seeing the same issues with
the back button and a few NotSerializableException lines in tomcat.log.
The Cat
Right - don't make your DAO serializable - the proxy thing should work.
Like Igor said, try a different container (run it up in Jetty with the
quickstart if you can - that should be quick and easy).
Let us know the results. If it still happens, let us see the code where you
define the category da
But if I have understood the docs http://cwiki.apache.org/WICKET/spring.html
here on the spring - annot project then categoryDao should be injected with
a serializable proxy which can get a categoryDao from spring when needed and
drop it when serialized.
Serkan Camurcuoglu-3 wrote:
>
> so ca
it shouldnt be happening. try deploying on something other then
glassfish like tomcat to see if its still happening.
-igor
On Thu, Jan 8, 2009 at 7:28 AM, quizzical wrote:
>
> Thanks, that seems to be the problem, I'm getting NotSerializableException,
> the offending objects are injected using @
so categoryDao implements java.io.Serializable but it cannot be serialized?
quizzical wrote:
Thanks, that seems to be the problem, I'm getting NotSerializableException,
the offending objects are injected using @SpringBean, which I thought
injected a proxy. I've read the docs online for spring-a
Thanks, that seems to be the problem, I'm getting NotSerializableException,
the offending objects are injected using @SpringBean, which I thought
injected a proxy. I've read the docs online for spring-annot and I can't see
why this should be happening.
I'm running glassfish and the log has this t
did you check your logs, if you are getting NotSerializableExceptions in
the background you may get page expired errors with back button..
quizzical wrote:
Hi everyone,
I'm in the process of writing an example ecommerce app to get to know wicket
and am really enjoying the experience.. At the
Ah, I get It. I thought we could count on direct object references to the
application level for at least the duration of the user session, but now i
see it's not a good idea, especially if you want proper back-button
functionality & serialization. LoadableDetachableModel sounds good, thanks.
igo
wicket can clone your model objects for versioning or serialize the
entire page to disk. it is not a good idea to hold direct references
to object's whose lifecycle is independent of wicket components, for
that you should use loadabledetachablemodel or something like it.
-igor
On Wed, Oct 29, 200
> After some debugging I solved it in a ugly way. I used PropertyModel() for
> the form and when I
> pressed submit the object did'nt update in a correct manner. I think it has
> to do with that the object is in the session.
Weird. Did you check that the target of the property model was the one
yo
After some debugging I solved it in a ugly way. I used PropertyModel() for
the form and when I
pressed submit the object did'nt update in a correct manner. I think it has
to do with that the object is in the session.
When I used Model() instead it worked.
--
View this message in context:
http:
I still don't get it. If I check another radio button and press submit it
would still do a post from wicket right?
--
View this message in context:
http://www.nabble.com/Back-button-problem-with-form-tp17512965p17574963.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
On Thu, 29 May 2008, Marieke Vandamme wrote:
> I noticed the same behavior in firefox, but for me everything works fine in
> internet explorer.
> My form is not working with ajax, but with the standard submit.
> Is it browser specific or can I change the behavior in my code?
Probably it depends
Hello,
I noticed the same behavior in firefox, but for me everything works fine in
internet explorer.
My form is not working with ajax, but with the standard submit.
Is it browser specific or can I change the behavior in my code?
Marie.
Mathias P.W Nilsson wrote:
>
> Hi!
>
> I have a form
Unfortunately that's not how it works now. So if you have ajax
application and don't want to get weird problems on back button the
only way now is to send the no-store header.
-Matej
On Fri, May 16, 2008 at 3:15 PM, Johan Compagner <[EMAIL PROTECTED]> wrote:
> i think that is more a problem of th
i think that is more a problem of the browser and i think that will be fixed
hopefully
the browser should always go to the latest dom it came from, not the file in
the cache..
johan
On Fri, May 16, 2008 at 2:18 PM, gumnaam23 <[EMAIL PROTECTED]> wrote:
>
> I guess you are right. But in an Ajax w
I guess you are right. But in an Ajax world, there really is no other way
around the problem, is there ?
Johan Compagner wrote:
>
> no i am against no-store as default.
>
> back button should be quick. If the line is a bit slow then users get very
> very very (i would) annoyed
> if the back b
no i am against no-store as default.
back button should be quick. If the line is a bit slow then users get very
very very (i would) annoyed
if the back button takes a while because it connects back to the server.
A back button shouldnt do that. I know we in wicket wants it to do it but
from an en
Mount your page using HybridUrlCodingStrategy.
-Matej
On Fri, May 16, 2008 at 11:01 AM, gumnaam23 <[EMAIL PROTECTED]> wrote:
>
> Adding "no-store" to the "Cache-Control" header did the trick.
>
> According to Page.setHeaders() javadoc , Wicket already adds cache related
> headers
> response.setHe
Adding "no-store" to the "Cache-Control" header did the trick.
According to Page.setHeaders() javadoc , Wicket already adds cache related
headers
response.setHeader("Pragma", "no-cache");
response.setHeader("Cache-Control", "no-cache, max-age=0, must-revalidate")
Is there any particular reason w
Are you sure you also send the cache-control: no-store header?
(no-cache is not enough). Also for opera there's no way to force the
reload.
-Matje
On Thu, May 15, 2008 at 9:40 PM, gumnaam23 <[EMAIL PROTECTED]> wrote:
>
> My back button, doesn't send request back to the server.
> I can see that th
my suggestion is to make it work without ajax first, that way you know
everything is correctly setup. then add ajax into the mix.
-igor
On Thu, Mar 27, 2008 at 4:46 AM, bhitai <[EMAIL PROTECTED]> wrote:
>
> Hi Igore
> I have some code to share now. This is what I did:
>
> in the constructor f
Hi Igore
I have some code to share now. This is what I did:
in the constructor for the Application, I mount pages with hybridUrlCoding
strategy as suggested by you.
mount(new HybridUrlCodingStrategy("home", MenuPage.class));
mount(new HybridUrlCodingStrategy("prod
So you see the initial state instead of the latest ajax state? This is
a browser problem, i believe ms is fixing that for ie in number 8.
You can go around it by letting the backbutton always go to the
server, look at configureResponse/setheaders of webpage an add nostore
On 3/27/08, bhitai <[EMA
Hi Igor
thanks for the prompt reply..I'm trying to figure out how exactly to do
that. This is because I have the following situation and I don't know where
to apply the url coding strategy:
1. there are two pages, one is a menu and one detail page
2. menu page displays objects in a hierarchy - to
mount your pages using hybridurlcodingstrategy
-igor
On Wed, Mar 26, 2008 at 12:05 PM, bhitai <[EMAIL PROTECTED]> wrote:
>
> I am a new wicket user, and have been trying to develop an application for
> the past few weeks. What I initially did was to use some databinder API to
> fetch persiste
Would appreciate peoples comments on the examples below, I believe they can
give a good idea to people who cant relate to the problems relating to
browser back-button and application state...which wicket solves with
versioning..
Example 1
Context : Your application follows a certain workflow w
It would be nice if an example of such ui interactions could be given...
On Mon, Mar 17, 2008 at 4:57 PM, Java Developer <[EMAIL PROTECTED]>
wrote:
> Been reading about wicket and would want to know the context in which the
> back button problem is being talked about..the only problem i have face
1 - 100 of 120 matches
Mail list logo
