vov wrote:
Is it possible to redirect user to the HomePage when new session is created?
@Override
public Session newSession(Request request, Response response)
{
//RequestCycle.get().setResponsePage(getHomePage());
//or
//RequestCycle.get().replaceAllRequestHandlers(new
Hi Stefan,
It's a good solution but I have external authentication system and only
thing that I know - is creation of the new session:(
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Redirect-to-the-HomePage-on-newSession-tp4656365p4656384.html
Sent from the
I cannot find anything related there. His blog started long after the book.
Am 14.02.2013 14:51 schrieb Ian Marshall ianmarshall...@gmail.com:
Perhaps a good source of information is Jonathan's blog at:
http://codeact.wordpress.com http://codeact.wordpress.com
Ian
Sebastian Gaul wrote
I think that, if you move your validations away from the fields, you will
be able to handle this situation and others very gracefully.
I usually perform my validations on the buttons, themselves.
It requires quite more typing, but gives maximum flexibility.
Elias
wicket_new_user
You could add a custom Behavior to your FormCompoments. Let this
Behavior implement IValidator and it will get notice of a form submit
via #validate().
Hope this helps
Sven
On 02/14/2013 07:05 AM, Alex wrote:
Hi. I have AjaxFallbackButton on the form with defined onSubmit handler.
There also
Hello,
We have just a situation were the information of the form needs to be
updated before handling an ajax click event.
The page has a form, with a bean and some TextFields that update the
properties in the bean.
It has also an ajax component that also updates the bean.
The problem is
Use AjaxFormSubmitBehavior with #setDefaultProcessing(false).
Sven
On 02/15/2013 11:01 AM, Gonzalo Aguilar Delgado wrote:
Hello,
We have just a situation were the information of the form needs to be
updated before handling an ajax click event.
The page has a form, with a bean and some
As I understand the only way to catch the form's onSubmit is by analyze form
components validation which is performed by form submitting. And if
validation is successful then form submit will be done for sure. Am I
correct understand?
Trying to find workaround for this issue,in MyCustomBehavior
Hi Everyone,
I'm using ModalWindows and AjaxEditableLabels and everything was working
fine for me.
But a stupid tester decided to use the return key(insted of just clicking
the next item) after he entered something in a AjaxEditableLable within a
ModalWindow.
This caused the Form created in
Let me give you more context:
my page consists of:
- a lazy loading autocompletetextfield
- a form containing the palette
By selecting an option in the autocomplete, the left side of the palette
(choices side) should display that selection made in the autocomplete.
So, I have so far managed to
Can anyone Tell me the reason for using a form at this location?
This is done to allow the following nesting:
body
--form Form [1]
div ModalWindow [2]
--div Form [3]
input FormComponent [4]
Note that in Wicket nested Forms [3] are rendered as divs.
When ModalWindow [2] pulls
On Thu, February 14, 2013, Fred!!! wrote:
it's possible to set an throtteling delay by Wicket AjaxRequestAttributes.
Have a look at
https://cwiki.apache.org/confluence/display/WICKET/Wicket+Ajax#WicketAjax-AjaxRequestAttributes
Something like this:
new AjaxEventBehavior(onkeydown){
Another thing I am stuck trying to port my project from Wicket
1.4.x to 6.6.0 is DND-mechanics which so far had been
implemented using wiquery 1.2.
As I see the 'DroppableAjaxBehavior' class has disappeared from
wiquery since the 6.0 release. However no mention could be found
on either migration
Hi,
It seems that behavior was not ported into 6.x branch. I have created
https://github.com/WiQuery/wiquery/issues/17
and will try to fix the issue ASAP.
On Fri, Feb 15, 2013 at 2:20 PM, Martin Dietze d...@fh-wedel.de wrote:
Another thing I am stuck trying to port my project from Wicket
The proposted patch in WICKET-3404 should really be in 7.
Thanks for explaining!
Sven Meier wrote
Can anyone Tell me the reason for using a
form
at this location?
This is done to allow the following nesting:
body
--
form
Form [1]
div
ModalWindow [2]
--
div
Form [3]
My mistake, I works great with the nullvalid.
I just realize that if I have an onchange behavior and a javascript
(jQuery) onchange function bind on the same dropdown, with IE, calling the
javascript onchange function will also call the wicket onchange behavior.
Can't figure out why.
--
View
You could always visit the Coding: On Software Design Process section of
Jonathan's blog (it's an excellent book, by the way) and ask him your
question from there.
Ian
Sebastian Gaul wrote
I cannot find anything related there. His blog started long after the
book.
Am 14.02.2013 14:51 schrieb
In data Thursday 14 February 2013 12:59:05, Sven Meier ha scritto:
Then the DropDownChoice should work fine.
Try to create a quickstart please.
You are so f***ing smart :)
The quickstart just worked and showed me what I was doing wrong, basically
this:
District currentSelection = ... //
Hi Francois,
Thanks, but actually this still has issues. At first I thought it was
clearly the simple thing I was missing, but then I remembered there's still
a problem - the line in renderHead copied from the original
MultiFileUploadField uses private members container, max, and upload, so the
I know I can preselect the value of DropDownChoice by setting the
corresponding value in the model.
My use case is this: I have several DropDownChoice with
OnChangeAjaxBehaviors. Selection of value in one DDChoice enables second
DDChoice. The values in second DDChoice depend on the value selected
Hi,
try something on the lines...
@Override
public void afterRender(Component component) {
component.getResponse().write(your HTML here);
}
THANK YOU!
It was exactly what I was looking for!
Works great.
Artur
-
To
#onConfigure() would be a good place to preselect something.
Sven
On 02/15/2013 05:21 PM, prasopes wrote:
I know I can preselect the value of DropDownChoice by setting the
corresponding value in the model.
My use case is this: I have several DropDownChoice with
OnChangeAjaxBehaviors.
You are so f***ing smart :)
Sometimes :P.
Sven
On 02/15/2013 04:43 PM, Lucio Crusca wrote:
In data Thursday 14 February 2013 12:59:05, Sven Meier ha scritto:
Then the DropDownChoice should work fine.
Try to create a quickstart please.
You are so f***ing smart :)
The quickstart just
Le 15 févr. 2013 à 16:48, evan e...@novelution.com a écrit :
Hi Francois,
Thanks, but actually this still has issues. At first I thought it was
clearly the simple thing I was missing, but then I remembered there's still
a problem - the line in renderHead copied from the original
Okay, so you are saying I need to create my own versions of each of those
private variables referenced in renderHead, and override any methods that
use any of them, to reference my own, is that right? Unfortunately, it
still has maintenance implications, but I guess that might just be
inevitable
DroppableBehavior is the replacement of DroppableAjaxBehavior. You use it
like this:
final DroppableBehavior droppableBehavior = new DroppableBehavior();
droppableBehavior.setDropEvent( new AjaxDropCallback() {
protected void drop(AjaxRequestTarget target, Component source,
Component dropped)
if the question is how to modify internal JavascriptResourceReference packaged
with component
I will just override
@Override
public void renderHead(IHeaderResponse response)
{
// initialize the javascript library
Hi,
I just added old AJAX behaviors for backward compatibility.
On Fri, Feb 15, 2013 at 8:28 PM, Emond Papegaaij
emond.papega...@gmail.comwrote:
DroppableBehavior is the replacement of DroppableAjaxBehavior. You use it
like this:
final DroppableBehavior droppableBehavior = new
28 matches
Mail list logo
