Hi Thomas,
No, there is no way to do what you need at the momemt.
Please file a ticket for improvement.
On Wed, Jan 9, 2013 at 1:13 AM, Thomas Götz wrote:
> Is there a way to manipulate/configure AjaxRequestAttributes globally (in
> Wicket 6.x)? My usecase: in every AJAX request I want to incl
Hi Cedric,
That's definitely an excellent idea to promote Wicket in France! :)
If you need help, I am there also!
Best regards,
Sebastien.
On Tue, Jan 8, 2013 at 8:55 PM, Pierre Goupil wrote:
> Good evening,
>
> Maybe three heads are better than two? If you need help, I'm there, guys!
>
> Regar
Emond,
Today I got the solution of this issue.
After contacting my hosting provider, we found out that the problem is that
Apache does not support proxying websockets via AJP or other protocols with the
currently installed modules.
References:
http://serverfault.com/questions/290121/configur
Ok, I stared at the code for a little longer and realized that I can use
the same principle - simply send the value to server, and return back
the new model value (most likely the same value).
Still, any comments below welcome :)
And, what would change if I wanted this also for Wicket 1.5? So f
I've looked at it, and the communication there revolves around JSON sent
for the component to show tags.
I haven't found how to send the HTML of the element.
Maybe I understand the concept wrong.
FWIK, Wicket has a small lib on client side which replaces HTML of
elements which are added to targ
Is there a way to manipulate/configure AjaxRequestAttributes globally (in
Wicket 6.x)? My usecase: in every AJAX request I want to include some
dynamicExtraParameters, i.e. client side information. Or is the only way to do
this to hook into one of the global ajax channels (e.g. "/ajax/call/befor
Emond,
I've tried it like you said and it almost works! It works in the sense that
I'm able to send an event to only one resource : that alone is fine in
itself.
But unfortunately, when doing: broadcaster.getAtmosphereResources() I don't
know which browser corresponds to which resource. So I defi
Good evening,
Maybe three heads are better than two? If you need help, I'm there, guys!
Regards,
Pierre Goupil
On Tue, Jan 8, 2013 at 6:52 PM, Francois Meillet wrote:
> Hi Cedric,
>
> I think it's a very good idea as Devoxx could help us to make Wicket
> better known in France.
> Ready to wo
Hi Cedric,
I think it's a very good idea as Devoxx could help us to make Wicket better
known in France.
Ready to work on that with you.
François
Le 8 janv. 2013 à 17:30, Cedric Gatay a écrit :
> Hi fellow Wicket'ers,
> I think many of you are aware of the second edition of Devoxx in Paris
---
You've been invited by Cedric Gatay to use Google Talk.
If you already have a Google account, login to Gmail and accept this chat
invitation:
http://mail.google.com/mail/b-f0f2595993-c7ed127545-Wz2ZkqxOQ31jTcb2t2vg9ldeQBA
To
> Hans, like Martin said, this doesn't work, and I already tried it. When
> you
> use those options, it just renders the element tag with no contents.
Yes, I realised that too. I am sorry if my answer caused you effort.
> Thank you very much, guys! When you come to Brazil, the beer is on me :)
Emond,
Thank you for your support. I will contact my provider about this.
Regards,
Noven
From: Emond Papegaaij
To: users@wicket.apache.org; Noven
Sent: Tuesday, January 8, 2013 7:27 PM
Subject: Re: Wicket Atmosphere does not run in Firefox 17
The quicks
Cool!
On Tue, Jan 8, 2013 at 2:54 PM, Carlson Weber wrote:
> Hans, like Martin said, this doesn't work, and I already tried it. When you
> use those options, it just renders the element tag with no contents.
> Martin, your solution is amazing. Simple and it just works. Thank you very
> much.
> Th
Ok i will try.
I've just check in 1.5.8 and you right, there is a behavior in
"renderComponentTag" which create *onchange=this.form.submIt(); *But after,
there is another behavior which overwrite the onchange attribut with
something like *onchange="var
wcall=wicketAjaxPost('?wicket:interface=b
Excellent, Emond! I'll try it like you said and tell you what happens.
Cheers,
Pierre
On Tue, Jan 8, 2013 at 1:55 PM, Emond Papegaaij
wrote:
> Hi Pierre,
>
> The UUID is bound to a page when atmosphere makes to call back to the
> server,
> which makes sense because before then, there is no Atm
Hi Pierre,
The UUID is bound to a page when atmosphere makes to call back to the server,
which makes sense because before then, there is no AtmosphereResource, which
means there cannot be a UUID. I think this is a bit of a design flaw, because
it is not possible to listen to the registration of
Hans, like Martin said, this doesn't work, and I already tried it. When you
use those options, it just renders the element tag with no contents.
Martin, your solution is amazing. Simple and it just works. Thank you very
much.
The solution was to and an AttributeModifier to the component and then I
Hi,
ChoiceFilter has option 'autoSubmit' which does:
if (autoSubmit)
{
choice.add(AttributeModifier.replace("onchange", "this.form.submit();"));
}
It seems you need to pass 'false'.
This code is the same in 1.5.x. I'm not sure why you see different behavior.
On Tue, Jan 8, 2013 at 1:04 PM, d
The quickstart does work on Firefox, but not on your provider. You should only
enable WS if your provider supports it. Atmosphere tries to autodetect the
capabilities of the browser and server to determine the best protocol to use.
For some reason, this system fails to detect that WS is not work
Hi,
In Wicket 6.4.0 i have a problem with ChoiceFilter in my AbstractToolbar.
When I check render HTML i have :
So when I change the value, my form is submit.
In Wicket 1.5.8, i don't have this behaviour. Could you tell me what's wrong
in 6.4 ?
Best regards,
Damien
--
View this message in
Emond,
Thank you for the link.
Btw didn't you find the quickstart does not work in firefox?
I will enable WS back and figure it out how to fix in firefox.
Regards,
Noven
From: Emond Papegaaij
To: users@wicket.apache.org; Noven
Sent: Tuesday, January 8,
Disabling WS will cause atmosphere to fall back on a different protocol, such
as http streaming or polling. WS is designed to support 2-way communication,
http is not. These other implementations might not be as reliable or might
consume more resources. This page contains a nice description of t
Hi,
Here is the source of
org.apache.wicket.markup.html.image.Image#getStatelessHint()
{
return (getImageResource() == null || getImageResource() ==
localizedImageResource.getResource()) &&
localizedImageResource.isStateless();
}
I.e. if the image uses a IResource then it is stateful because the
Have you tried with ContextImage?
Hi - I would like to link to a static image, and the link should be
stateless.
I have tried this (using Scala):
val img = new Image("img", new ContextRelativeResource("images/img" + imgId
+ ".png"))
But the link becomes stateful.
I just found
val img = new I
24 matches
Mail list logo