;
> On 21.06.19 15:01, Francois Meillet wrote:
> > When I send an email to users@wicket.apache.org users@wicket.apache.org> I receive this automatic email from
> p.davids@hea.jetzt <mailto:p.davids@hea.jetzt>
> >
> > Guten Tag,
> > die E-Mailadresse des Empfän
Hi,
that's just an automatic reply from Patrick's mailbox.
@Patrick check your subscription please
Have fun
Sven
On 21.06.19 15:01, Francois Meillet wrote:
When I send an email to users@wicket.apache.org <mailto:users@wicket.apache.org> I
receive this automatic ema
When I send an email to users@wicket.apache.org
<mailto:users@wicket.apache.org> I receive this automatic email from
p.davids@hea.jetzt <mailto:p.davids@hea.jetzt>
Guten Tag,
die E-Mailadresse des Empfängers hat sich geändert.
Gern leiten wir Ihre E-Mail weiter.
Bitte ändern Sie fü
I didn't find a way to tell if the page was loaded from the browsers cache.
I found a work around that's specific to our application but doesn't really
solve my initial question.
Thanks
On Fri, Apr 29, 2011 at 9:53 AM, Jeremy Thomerson wrote:
> Please post for future people who find this thread.
Please post for future people who find this thread.
On Thu, Apr 28, 2011 at 5:41 PM, Matthew Goodson
wrote:
> I finally managed to figure out a workaround for this so it's all workin
> now.
> Thanks for your help!
>
> On Fri, Apr 29, 2011 at 8:49 AM, Matthew Goodson
> wrote:
>
> >
> > Yeah on the
I finally managed to figure out a workaround for this so it's all workin
now.
Thanks for your help!
On Fri, Apr 29, 2011 at 8:49 AM, Matthew Goodson
wrote:
>
> Yeah on the javascript side it will fire off a request to the server to
> reload the tab each time. But wicket on the server thinks that
Yeah on the javascript side it will fire off a request to the server to
reload the tab each time. But wicket on the server thinks that the requested
tab is already loaded so ignores the request
On Thu, Apr 28, 2011 at 9:07 PM, Martin Grigorov wrote:
> The random parameter is there to prevent cach
The random parameter is there to prevent caching of the Ajax response.
AFAIK clicking on a tab will reload its content each time. I.e. Wicket
doesn't "think that the tab is already loaded".
On Thu, Apr 28, 2011 at 12:41 AM, Matthew Goodson
wrote:
> Yeah I'm not feeling too hopeful
> I have a tabb
Yeah I'm not feeling too hopeful
I have a tabbed panel which loads the tabs via ajax. When the page is loaded
from the browsers cache i.e. the user hits the back button, the ajax request
to load the tab is sent but wicket thinks that tab is already loaded
(getSelectedTab()) so ignores the request.
Hi,
I'm not sure whether this is possible at all.
Why do you need to do this ?
On Wed, Apr 27, 2011 at 8:12 AM, Matthew Goodson
wrote:
> Hi guys,
> I'm trying to find out if an ajax request has come from page that was loaded
> from the browsers cache. Does anyone have any ideas of how I could ac
Hi guys,
I'm trying to find out if an ajax request has come from page that was loaded
from the browsers cache. Does anyone have any ideas of how I could achieve
this?
Thanks
Replying to myself;
Ah, OK, I just need to do this in the testcase:
private WicketTester tester = new WicketTester(new WicketApplication());
Sweet.
T P D wrote:
I've created a Wicket project using the Maven archetype provided at:
http://wicket.apache.org/quickstart.html
I've created a class
See WicketTester. It handles all of that for you and gives you a lot of
extra abilities to test Wicket components, pages, etc.
Also covered in Wicket in Action, as well as this page appearing when you
Google "wicket unit test":
http://cwiki.apache.org/WICKET/unit-test.html
--
Jeremy Thomerson
ht
I've created a Wicket project using the Maven archetype provided at:
http://wicket.apache.org/quickstart.html
I've created a class inherited from a Wicket Component.
I've created a JUnit4 testcase subclass to unit test my class. It just
news up an instance of my Component-derived class, and cal
14 matches
Mail list logo
