Hi,
It is OK.
But you can also just update some field/model in the current page instance.
On Fri, Feb 8, 2013 at 7:00 AM, snair sreelatha.n...@transport.wa.gov.auwrote:
Is it ok to call the same page using setResponsePage(), only calling a
different constructor, since the page now needs to
Hi,
I've found the same issue as yours and opened [1] with a simple patch.
Regards.
[1] https://issues.apache.org/jira/browse/WICKET-5029
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Palette-and-localization-tp4495234p4656195.html
Sent from the Users forum
Martin.
Thanks for your answer!
Yes, that approach would be a cleaner. What I was hoping was to be able to
do the mounting cleanly inside component... But then I would have to keep a
constant with /some/path... which would amount the the same kind of non
DRYness.
On Thu, Feb 7, 2013 at 5:18 PM,
What is your reason to use a mounted resource ?
- nice looking url ?
- avoid synchronization on the page
If these two are not hard requirements then you can use
IResourceListener/IBehaviorListener, so each component will have its own
mount point.
On Fri, Feb 8, 2013 at 9:37 AM, Ernesto Reinaldo
Hi,
On Fri, Feb 8, 2013 at 9:42 AM, Martin Grigorov mgrigo...@apache.orgwrote:
What is your reason to use a mounted resource ?
- nice looking url ?
I want the component to be stateless...
- avoid synchronization on the page
If these two are not hard requirements then you can use
Hi,
On Fri, Feb 8, 2013 at 9:42 AM, Martin Grigorov mgrigo...@apache.orgwrote:
What is your reason to use a mounted resource ?
- nice looking url ?
- avoid synchronization on the page
If these two are not hard requirements then you can use
IResourceListener/IBehaviorListener, so each
Hi,
Just override :
@Override
public boolean getDefaultProcessing()
{
return defaultProcessing;
}
On Fri, Feb 8, 2013 at 11:11 AM, wicket_new_user murthy.m...@gmail.comwrote:
Hi,
i'm having an issue where the form is getting submitted, when
AjaxFormSubmitBehavior is being used.
I see we
Hi,
This is what I like about Wiket.
Even if I start with a stateless page! So I update a component, and
Wicket takes care of it via server side state - job done.
The page is then no longer stateless which is fair.
But:
When the user stays on this page and the session expires, then even
Hi,
On Fri, Feb 8, 2013 at 11:44 AM, Bernard bht...@gmail.com wrote:
Hi,
This is what I like about Wiket.
Even if I start with a stateless page! So I update a component, and
Wicket takes care of it via server side state - job done.
The page is then no longer stateless which is fair.
Thanks Igor, that worked.
As a hint to future bootstrapping wicketeers:
remove the all data-toggle, href, data-target etc attributes
and the $('#myModal').modal(); call.
put the modal's body in a container div.
then render the dialog content using AJAX like
new AjaxLink(EditAjax) {
10 matches
Mail list logo