Hi,
On Mon, May 27, 2013 at 8:35 AM, Dirk Forchel dirk.forc...@exedio.comwrote:
You mean setStatelessHint(true) should be enough to simulate that it is
stateless (and not setStatelessHint(false)), do you?
Yes, sorry.
Actually we didn't care about whether a page is stateless or not as
Hi,
I guess you know that History API (pushState) works only in IE10, all older
versions of IE do not support it.
About your question: you can use AjaxRequestTarget#addChildren(getPage(),
AbstractLink.class) to add all links in the current page to be repainted.
Wicket uses
Hello Martin,
Is it possible to know current URL (used by the user if reverse proxy is
used)?
On Mon, May 27, 2013 at 2:34 PM, Martin Grigorov mgrigo...@apache.orgwrote:
Hi,
I guess you know that History API (pushState) works only in IE10, all older
versions of IE do not support it.
Hi Andy,
As far as I know there is no more generic way to do the same.
There is a open ticket about this with an idea how to approach this but so
far no one worked on it.
On Fri, May 24, 2013 at 9:07 PM, Andy Van Den Heuvel
andy.vandenheu...@gmail.com wrote:
Hey,
I was looking for a good
Hi Maxim,
For Wicket the client is the proxy, so the request url is what the proxy
sends to the servlet container.
If the proxy sets the original url in a request header then the application
code can read this header and use it.
On Mon, May 27, 2013 at 10:37 AM, Maxim Solodovnik
Hi,
I just fixed the issue. It should hit Maven Central soon.
On Sat, May 25, 2013 at 12:13 PM, Per Newgro per.new...@gmx.ch wrote:
Ok, i've delete all wicket 8.8.x jars from m2. But the problem still
appears. It seems that wicketstuff-annotations is referencing
wickt-6.8.0-SNAPSHOT.
I
Hello!
I have such a weird problem i dont think i will be able to explain it in
one shot, i'll try anyway.
The thing is have a page (a class that descends from WebPage) that uses a
popup (using a class that descends from ModalWindow), and the popup itself
shows a new popup (again, by using a
Hi,
I guess you already know that Wicket serializes the pages at the end of the
request cycle.
After deserialization the object id is no more the same as the one before
serialization.
You should not rely on same JVM instance.
Check Wicket-Examples demo for ModalWindow. It uses PageReference to
Actually I don't see any reason why to redirect for stateless pages, but
browsing the source code I found that the default WePageRenderer returns
true for
org.apache.wicket.request.handler.render.PageRenderer.enableRedirectForStatelessPage().
Should I override this method as well to disable the
Well, you can't serialize the BufferedImage, but maybe you can serialize
whatever data you've used to render BufferedImage's contents,
i.e. instead of saving the image, save whatever is necessary to recreate
the image?
Or, you could store the BufferedImage's content to an actual image file
(using
Hi wicket community,
i have a question about how to implement a confirm dialog via javascript on a
button or link. Before wicket 6 we used a simple behavior (as mentioned here:
https://cwiki.apache.org/WICKET/getting-user-confirmation.html) which could be
used to enrich any button or link
Hi Marcel,
What exactly is the issue with non-Ajax links ?
On Mon, May 27, 2013 at 12:34 PM, Marcel Hoerr marcel.ho...@gmx.de wrote:
Hi wicket community,
i have a question about how to implement a confirm dialog via javascript
on a button or link. Before wicket 6 we used a simple behavior
https://issues.apache.org/jira/browse/WICKET-1177
On Mon, May 27, 2013 at 12:44 PM, Andy Van Den Heuvel
andy.vandenheu...@gmail.com wrote:
What's the ticket number?
On Mon, May 27, 2013 at 9:47 AM, Martin Grigorov mgrigo...@apache.org
wrote:
Hi Andy,
As far as I know there is no
I solve this problem by making the BufferedImage transient.
2013/5/27 Jonas barney...@gmail.com
Well, you can't serialize the BufferedImage, but maybe you can serialize
whatever data you've used to render BufferedImage's contents,
i.e. instead of saving the image, save whatever is necessary
Hi Martin,
the suggested solution needs AjaxRequestAttributes in order to display the
confirm dialog. In an non Ajax setting there would be no ajaxrequest though.
Best regards
marcel
Am 27.05.13 um 11:37 schrieb Martin Grigorov
Hi Marcel,
What exactly is the issue with non-Ajax
Hi Marcel,
But the solution with onclick attribute is still valid for non-Ajax link.
You can use it for Ajax link too - returning false will stop the execution
of the bound event listener used by Wicket to do its work.
On Mon, May 27, 2013 at 2:02 PM, marcel.ho...@gmx.de wrote:
Hi Martin,
Hi all,
In app I have several pages on http on those pages I need https link to the
LoginPage.
I have set HttpsMapper as a root mapper and added RequireHttps to the
LoginPage class.
I'm using Wicket 6.8.0
--
View this message in context:
Hi Alexey,
Wicket generates relative urls.
When the user clicks the link to LoginPage HttpsMapper will check that
LoginPage requires HTTPS and
that the current protocol is HTTP and will make a redirect with HTTPS.
So it will work automatically, with the price of an additional redirect.
On Mon,
Hi Martin,
Thanks for the super fast reply!
In my case I have no redirect, Login page opens with HTTP, but in the form
(in action attribute) I see correct HTTPS url.
Will try to reproduce in the Quickstart.
--
View this message in context:
Hello Martin! Thanks for the quick reply!
Indeed, i was aware that after a serialization/deserialization the JVM
instance will not be the same, however, my problem is that attribute values
are not maintained (or at least the right objects are not being used)
i found out the following by
Hi Rafael,
Please create a quickstart and attach it to Jira or upload it somewhere so
we can debug it.
I'm sure you leak Page instances and this causes the problem.
As I already suggested - you should use PageReference to get to the outer
page(s).
On Mon, May 27, 2013 at 10:50 PM, Rafael Barrera
Hi,
when I want to manage the 'before' and 'complete' handlers of an ajax
component, everything works as expected if I override the component
updateAjaxAttributes method of the component like in the below example:
public class HomePage extends WebPage {
public HomePage(final
I forgot to mention that the example is built with wicket 6.8.0
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/IAjaxCallListener-issues-in-AbstractDefaultAjaxBehavior-updateAjaxAttributes-tp4659055p4659056.html
Sent from the Users forum mailing list archive at
Hi,
you're adding an additional behavior that has nothing to do with the
behavior created in AjaxLink#newAjaxEventBehavior().
SomeAjaxBehavior#updateAjaxAttributes() and #respond() are never invoked.
Sven
On 05/27/2013 10:22 PM, stefanofg wrote:
on the other hand, if I create an
On Mon, May 27, 2013 at 11:33 PM, Sven Meier s...@meiers.net wrote:
Hi,
you're adding an additional behavior that has nothing to do with the
behavior created in AjaxLink#newAjaxEventBehavior(**).
SomeAjaxBehavior#**updateAjaxAttributes() and #respond() are never
invoked.
Correct.
You
Thanks a lot Sven and Martin.
Extending my behavior from AjaxEventBehavior solved the problem for now,
even though when I use that behavior, I must be aware of the event managed
by the component.
--
View this message in context:
Martin,
Awesome - thanks, once again...!
That gives me plenty to get on with... :)
Cheers,
Col.
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: 27 May 2013 17:34
To: users@wicket.apache.org
Subject: Re: Panel switching
Hi,
I guess you know that History
27 matches
Mail list logo
