Hello again,
I have a question regarding localization in drop downs.
I need the options inside the drop down to be localized. When I change the
language, the options are not changed. Only if I
access the page again.
Here is how I implemented the getDisplayValue method in ChoiceRenderer:
return ne
Thanks Sven. Unfortunately we can't test without the CSS, otherwise it's all
just text. Any other ideas?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Spacing-IE7-Issue-when-doing-Wicket-setVisible-on-WebMarkupContainer-tp4661733p4661752.html
Sent from the Users fo
Thank you both for your feedback, everything is in place now.
For the record, the code that generates the required javascript now is:
"$('#" + markupId + "').on('blur', '.df', function() {var comp =
$(this).attr('name'); var cid=$(this).attr('id'); var data = {};
data['component']=comp; Wicket.Aj
Happily, we fixed this IE7-only problem.
All we had to do was add the top-level Repeater (containing all the panels)
to the Ajax target of the AjaxCheckbox triggering the visibility of these
child panels.
final AjaxCheckBox HQUserCheckBox = new AjaxCheckBox("HQUser", new
PropertyModel(formObject,
This link might be useful too
https://github.com/reiern70/antilia-bits/tree/master/wicket-sparelinks
On Tue, Oct 8, 2013 at 9:31 PM, Marios Skounakis wrote:
> Hi all,
>
> I want to implement an ajax behavior similar to
> AjaxFormComponentUpdatingBehavior but which can be attached only once t
Hi,
take a look at AjaxFormChoiceComponentUpdatingBehavior on how to add
dynamic parameters to Wicket's ajax calls. Read
https://cwiki.apache.org/confluence/display/WICKET/Wicket+Ajax#WicketAjax-AjaxRequestAttributes
too.
Sven
On 10/08/2013 09:31 PM, Marios Skounakis wrote:
Hi all,
I want
Hi all,
I want to implement an ajax behavior similar to
AjaxFormComponentUpdatingBehavior but which can be attached only once to a
parent container component and issue ajax calls for all contained form
components.
So what I did was extend AbstractDefaultAjaxBehavior and pretty much copy
the logic
Ok, so I'll have to either introduce conditions in the code to check if
I am running the application in test mode
or use something else like a selenium perhaps..
Thanks anyway.
On 8.10.2013 14:08, Martin Grigorov wrote:
WebSocketTester is for Native WebSockets, not for Wicket-Atmosphere
integra
Hi,
in which files do you keep your localized strings? *.properties,
*.properties.xml or *.utf8.properties?
Sven
On 10/08/2013 05:49 PM, cosmindumy wrote:
Solved the localization problem.
I didn't know wicket convention about localization in choices.
There is still the problem with utf-8.
Th
Solved the localization problem.
I didn't know wicket convention about localization in choices.
There is still the problem with utf-8.
Thanks.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-localize-options-in-drop-down-tp4661751p4661753.html
Sent from the
On Tue, Oct 8, 2013 at 2:44 PM, Vit Rozkovec wrote:
>
> Thank you, I'll check it out.
>
WebSocketTester is for Native WebSockets, not for Wicket-Atmosphere
integration.
> v.
>
>
> On 8.10.2013 12:09, Martin Grigorov wrote:
>
>> Yes, because WicketTester doesn't use web.xml/atmosphere.xml.
>> T
Thank you, I'll check it out.
v.
On 8.10.2013 12:09, Martin Grigorov wrote:
Yes, because WicketTester doesn't use web.xml/atmosphere.xml.
The bootstrap of Atmosphere should be done manually. But I'm not sure that
even this will be enough. WicketTester doesn't do real http calls, so
Atmosphere w
In normal production mode everything is ok,
but the problem is when unittesting atmospherised wicket application
with WicketTester as application trips on init() method when
inicializing EventBus.
And I did not wanted to check in the code whether I am in test mode to
disable atmosphere calls.
Hi Sven,
Hi,
the Border will add your input into its body, so its effective path
will be "loginNameBorder:body:loginName".
Almost :-) Maybe this was changed in more recent versions but for 1.5.8
it's "loginNameBorder:loginNameBorder_body:loginName"
Thanks for the hint, much appreciated !
Hi,
the Border will add your input into its body, so its effective path will
be "loginNameBorder:body:loginName".
Sven
On 10/08/2013 12:29 PM, Tobias Gierke wrote:
Hi,
In one of my pages I have a textfield (whose visibility is changed
through AJAX) that is wrapped with a border like so:
Hi,
In one of my pages I have a textfield (whose visibility is changed
through AJAX) that is wrapped with a border like so:
>8->8->8-
:
wicket:id="loginName"/>
>8---
Yes, because WicketTester doesn't use web.xml/atmosphere.xml.
The bootstrap of Atmosphere should be done manually. But I'm not sure that
even this will be enough. WicketTester doesn't do real http calls, so
Atmosphere won't be able to process them.
You can see WebSocketTester in Native WebSocket m
The WicketRuntimeException says that there is no Atmosphere
BroadcasterFactory configured
On Tue, Oct 8, 2013 at 11:58 AM, Martin Grigorov wrote:
> On Tue, Oct 8, 2013 at 12:55 PM, francois meillet <
> francois.meil...@gmail.com> wrote:
>
> > Did you include the atmosphere.xml configuration file
On Tue, Oct 8, 2013 at 12:55 PM, francois meillet <
francois.meil...@gmail.com> wrote:
> Did you include the atmosphere.xml configuration file and configured the
> AtmosphereServlet ?
>
He asks about WicketTester+Atmosphere.
>
> François
>
>
> On Tue, Oct 8, 2013 at 11:26 AM, Vit Rozkovec
> wr
Did you include the atmosphere.xml configuration file and configured the
AtmosphereServlet ?
François
On Tue, Oct 8, 2013 at 11:26 AM, Vit Rozkovec wrote:
> Any hints, please?
>
> Vit
>
>
> On 6.10.2013 17:43, Vit Rozkovec wrote:
>
>> How is it possible to unit test Wicket application that use
Any hints, please?
Vit
On 6.10.2013 17:43, Vit Rozkovec wrote:
How is it possible to unit test Wicket application that uses Atmosphere?
When I run the application everything is ok, when testing, see excerpt
of the stacktrace -
org.apache.wicket.WicketRuntimeException: There is no Atmosphere
21 matches
Mail list logo