am trying the same example , But could you show us the autheticator java
class :)
Mine is :
package org.example.myapp.services;
public class UserAuthenticator {
public String userName;
public String password;
public String getUserName() {
return userName;
For god's shake, thanks a lot for your response,Hugo! I was trying something
different for activate validations in both sides, but, due to the
restrictions I think I'm gonna follow your idea.
Thanks a lot again for your time :D
--
View this message in context:
It sure is possible.
Looking at your use case my approach would be to implement those conditional
validation on the onValidateForm method in your page / component class.
For example:
public class Login
{
@Persist
@Property
private String userId;
@Property
private String password;
You can bind your validators dynamically
(validatory=ognl:conditionalValidStuff )
and submit changes of you pre-conditions via @EventListener.
Sounds a bit like overkill for simple dependencies, but can do very
complex things
-Original Message-
From: Drew McAuliffe [mailto:[EMAIL
http://tapestry.apache.org/tapestry4.1/usersguide/validation.html
http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/form/validator/Identity.html
Look at the match/differ validators. The cover the basic concept of a
validator that acts on two components. You can probably write
The problem with the identity validator is that it doesn't seem to capture
the current value of the other control, which is the essential problem I'm
having. If you have 2 controls, and the second one uses an identity
validator to make sure it's the same as the first, if you change them both
at
looks like a bug then - you could add a JIRA
On Dec 21, 2007 11:51 PM, Drew McAuliffe [EMAIL PROTECTED] wrote:
The problem with the identity validator is that it doesn't seem to capture
the current value of the other control, which is the essential problem I'm
having. If you have 2 controls,
Steve Shucker wrote:
I need everything in one form
because the checkbox states should be persisted even when the popup
dialog is submitted.
[...]
My options as I see them:
[...]
- use a separate form with an async submit for the popup (may work,
but then I'd have to return some javascript to
Http only submits one set of form data. If I have two forms, only the
data from the form I submit is transmitted back to the server. Tapestry
wouldn't receive the other information I want to persist. An async
submit would get around this by not re-rendering the page to avoid
losing the
Steve Shucker wrote:
Http only submits one set of form data. If I have two forms, only the
data from the form I submit is transmitted back to the server.
Tapestry wouldn't receive the other information I want to persist.
An async submit would get around this by not re-rendering the page to
10 matches
Mail list logo
