I added a ajax event handler to the checks in my pageable list view like this
add(new AjaxEventBehavior("onclick") {
@Override
protected void onEvent(AjaxRequestTarget target) {
List list = (List) checkGroup.getModelO
I created a quickstart project to reproduce the error. Curiously, the problem
does not show up in the automated test case. It does show up however if you
run jetty and then click "TabbedPanels"-->"intercept"-->"Tabbed Panel".
The difference between the test case and the browser variant seems to
a issue: https://issues.apache.org/jira/browse/WICKET-1478
>
> but I'm sure you don't mean that behaviour as you certainly searched the
> list and the jira before posting, am I right? ;-)
>
> regards
> Michael
>
>
> ckuehne wrote:
>>
>> I have the fo
Pills wrote:
>
> iirc, onBeforeRender must always call super.onBeforeRender.
>
> so put super.onBeforeRender on the first line.
>
>
Thanks for the quick reply. Unfortunately the super.onBeforeRender call does
not solve the issue.
--
View this message in context:
http://www.nabble.com/U
I have the following use case:
I go from Page A to Page B passing an instance of A as return page to B. In
B I click a link which brings me back to the (cached(?)) instance of A. In
the onBeforeRender-method of a child component of A I want to redirect if
some condition is
prot
My problem is as follows:
I have a bookmarkable page with an AjaxTabbedPanel as a component. If one of
the page parameters contains a forward slash "/" I get a weird behavior.
Firefox generates the following URL
a)
...¶m=value1/?wicket:interface%3D:73:lemmasTabpanel:panel:workstepsTabpanel:tabs-
I'm doing drag and drop operations with an implementation of
org.apache.wicket.markup.html.tree.BaseTree. For the drop event I call
...
dropNode.add(dragNode);
tree.repaint(target);
...
However I get an IllegalStateException when processing the ajax request (in
detach(RequestCycle)) because so
equest makes no difference as long as you
> don't rerender the component during an ajax request.
>
> -Matej
>
> On Jan 19, 2008 9:51 PM, ckuehne <[EMAIL PROTECTED]> wrote:
>>
>> I don't want it to be cached across ALL requests. If the site is reloaded
&g
If I put the autocomplete field on a panel that is added and replaced
dynamically via ajax it does not work in
Internet Explorer (tested with ver. 7) anymore. In Firefox everything is
alright. In IE also if the ac-field is visible when the page is loaded. But
when I add it later on dynamically vi
g an ajax request.
>
> -Matej
>
> On Jan 19, 2008 9:51 PM, ckuehne <[EMAIL PROTECTED]> wrote:
>>
>> I don't want it to be cached across ALL requests. If the site is reloaded
>> I
>> want
>> the model detached and reloaded as well. But not so be
e data is loaded
> when needed, if you want it to be cached across request you need to
> implement your own model.
>
> -Matej
>
> On Jan 19, 2008 6:28 PM, ckuehne <[EMAIL PROTECTED]> wrote:
>>
>> Just out of curiosity: I noticed that when I add a component to
Just out of curiosity: I noticed that when I add a component to an
AjaxRequestTarget a detach of the component's parent page
(component.getPage()) is triggered. Is there a way around this behavior?
I have a listview on that page with a LoadableDetachableModel and I'd rather
like that to be reloade
I call setRespongePage() in the ajax onchange handler of the autocomplete
field. The behavior seems buggy in the case when the user did not select a
choice but submitted the input of the field with ENTER. If there are no
choices for the entered text then everything works fine. But if there are
ava
Thanks, that was very helpful.
Conny
Eelco Hillenius wrote:
>
> On Jan 14, 2008 3:49 PM, ckuehne <[EMAIL PROTECTED]> wrote:
>>
>> Hi,
>>
>> I don't quite know what to do with the following debug message. The
>> AddPanel.html is definetely where
Hi,
I don't quite know what to do with the following debug message. The
AddPanel.html is definetely where
it should be (wicket bench finds it as well). I am also curious where the $3
comes from?
The problem did not occur in 1.3 RC2. But then again I made some changes
after updating to 1.3 final
a
e the id's of the
autocomplete selections the workaround was straightforward: I hooked the
onchange event to the hidden field and made the
autocomplete javascript fire an onchange on the hidden field.
ckuehne wrote:
>
> In the use case from the ajax autocomplete example the field gets
&
In the use case from the ajax autocomplete example the field gets submitted
when the selection
is made with the mouse. Is there a quick way to fix this?
Conny
--
View this message in context:
http://www.nabble.com/Autocomplete-Textfield-gets-submitted-twice-on-mouse-click-tp14777002p14777002.ht
Hi,
I'd like my AutoCompleteTextField to behave as follows
- I want the names of my list items displayed (item.name)
- when I select one I want the item.name displayed in the AC-TextField
So far, so good. But ...
- internally I want the item.id put into the request in order to select the
obje
18 matches
Mail list logo