As a user I would be surprized if my selection in drop down caused dialog
opened. I would be surprized more if some values were not be possible to
select.
--
View this message in context:
You're not alone.
I upgraded to wicket 1.4.11 and noticed that the ajax handling was broked.
Rolled back to 1.4.10 and ajax handling was broken. Ctrl+R in FF helped.
Probably something is wrong in wicket-ajax.js?
--
View this message in context:
I don't like subscriptions implementation. Somewhen it becomes difficult to
realize when to add/remove observers. It depends on the order of
instantiations. Visitor pattern seems to be much more reliable.
--
View this message in context:
There is JIRA issue for the problem
https://issues.apache.org/jira/browse/WICKET-2933
https://issues.apache.org/jira/browse/WICKET-2933
Igor I believe what you wrote works fine for single form. But when the page
contains nested forms the outer form still finds component - inner form.
--
View
The sources shows that the markup container is initialized prior to children
initialization. As expected. I used to double check due to onBeforeRender()
method. Should javadoc mention aforementioned?
The great news is that onBeforeRender() will never be used for component
initialization just for
Igor,
Having played with multi-line data tables I realized that there isn't an
easy way to extend the basic DataTableT. The multiline data table has a
customizable layout where cell has collspans and possibly rowspans. It means
that the configuration is not simple list of columns. It makes the
Since you wrote that you employ Spring MCV I presume you don't use any page
state when constructing your dynamic resource, instead you parse URL
parameters. Thus your resource seems to be shared resource.
I used to extend WebResource (provide your own dynamic implementation of
IResourceStream)
