Thanks for the explanations, much appreciated to all.
Peter
- Original Message -
From: "cordenier christophe"
To: "Tapestry users"
Sent: Wednesday, 7 October, 2009 15:07:52 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Validation question - at whic
Hi
The solutions suggested by Dirk and Urlich sounds good to me.
Actually, in the submission process the target variable set with 'value'
attribute is modified only if validation succeeds. This is why your code
doesn't work.
Christophe.
Anybody?
- Original Message -
From: "Peter Stavrinides"
To: "Tapestry Mailing List"
Sent: Tuesday, 6 October, 2009 10:07:53 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Validation question - at which point are property values set before
post
Hi ever
:
Validation question - at which point are property values set before post
They seem to be set after the input field validators complete.
//This code works
public void onSuccess() throws SQLException {
if(isTerminated()){
if(personnelData.getEndDate() == null
Peter Stavrinides schrieb am 06.10.2009
09:07:53:
> Validation question - at which point are property values set before post
They seem to be set after the input field validators complete.
>
> //This code works
> public void onSuccess() throws SQLException {
>
>
Hi everyone,
I came across what seems a strange scenario to me, using Tapestry 5 validation.
I am looking for a little understanding more than anything else with regards to
'the point at which properties values are set, before a form posts'... please
examine this code snippet:
//This code wor
()
onValidateFormFromLoginForm();
With a single form, you may just want to use onValidateForm().
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 06, 2008 08:46
> To: users@tapestry.apache.org
> Subject: Form validation quest
From reading the documentation I am under the impression that during
form submission a VALIDATE_FORM event is emitted once. However, I
observe onValidate() being called for every component in the form, the
value from the component not being set until *after* onValidate has
apparently been c
Very good. For completeness for anyone else reading this, I did the
following:
Added to the java class
@Component
private BeanEditForm _form;
public BeanEditForm getForm()
{
return _form;
}
and changed template to ( notice the
Thanks!
Filip S. Adamsen wrote:
> Hi Chris,
>
> Simply inj
Hi Chris,
Simply inject the BeanEditForm into your page class and use that to
record the errors. You'll need to give the BeanEditForm an id in your
template and then use the @Component annotation to inject it.
Details are here:
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/
Simple question from a noob: Following form example, mostly works
well. Now I want to do some cross validation server side, and can do
that, however I cannot figure out how to set the error message on
the form.
My class has:
@Inject
private BeanModelSource _beanModelSource;
@Inject
priva
Hi -
How can I make sure that whenever I select an invalid value from a
poplist - according to my validator -
this faulty value is still selected when the form is redisplayed?
Currently the poplist (selected) value
'rolls back' to the value it had prior to the invalid selection.
Thanks,
-J.
Never mind, I'm using commons-validator for that. I really would like
to see a way of bypassing validation on the table component
navigation, clearing the delegate for the form after the component
finish rendering??? I wonder if it is a validation request for a JIRA
enhancement?
Regards
On 10/2/
Hello there! I need to validate my fields by hand (table component
navigation issues :) )
I'd like to know if its possible to use the validators on my listener
instead of binding them? If so, how?
For instance:
IFormComponent name = (IFormComponent)getComponent("name");
//validate the name usin
I'll throw in my endorsement for (1). Often, we programmers get too
wrapped up in try to use some clever framework feature for every
minute detail ... when sometimes, it's simpler just to write a few
lines of code.
A listener which first performs validation before processing is easy
to wr
AhhI really need to finish up the 4.1 release. We'll be able to support
arbitrary requirements logic like this now as well. (on the client side &&
server.. Ie if this field gets filled out/selected then these other two
fields are required. Stuff like that)
On 7/3/06, Richard Clark <[EMAIL PRO
You can either:
1) Do all the validation in your listener (on the Java side), or
2) Write your own client-side valdation code in JavaScript.
The server-side validation would look like this:
ValidationDelegate delegate = (ValidationDelegate)getComponent("delegate");
if (!getCheckbox()) {
String
Labas Aleksej, Hi Shing,
thanks for the answers.
I think Aleksej's solution is simpler and it fits. But the bad thing is i'll
have to say a good bye to client side validation..
Valdemaras Repšys
On 7/3/06, Aleksej <[EMAIL PROTECTED]> wrote:
bėgantis debesis wrote:
> Hi,
>
> to simplify a prob
bėgantis debesis wrote:
Hi,
to simplify a problem, let's say i have a @Checkbox and many @Text
components in a form.
I want no validation when the checkbox is checked, and validation must be
executed, when form is submitted with the checkbox not checked. @Text
component contents must be validate
I do not have an easy solution to your problem.
The following is just an idea which I have not tested.
Have you considered 'extending' the component
TextField
to hava an extra boolean parameter 'validation flag'
?
The idea is that validation is skipped according to
the
'validation flag'. In you
Hi,
to simplify a problem, let's say i have a @Checkbox and many @Text
components in a form.
I want no validation when the checkbox is checked, and validation must be
executed, when form is submitted with the checkbox not checked. @Text
component contents must be validated.
Do you know any ways o
21 matches
Mail list logo
