Hi all
I've been knocking my head on the wall trying to find whats wrong here, and
I can't see anything.
I have a set of fields, inside a form, in an html snippet I defined as a
component. I created a html file that contains just a snippet of that file,
a .jwc file that contains the definition
I have no problem with validators for a TextField
within a custom component.
You might like to post your component's .java, .jwc.
and .html and see if anyone in the list can help.
Shing
--- Rui Pacheco [EMAIL PROTECTED] wrote:
Hi all
I've been knocking my head on the wall trying to
Here they go:
This is my .jwc:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE component-specification PUBLIC -//Apache Software
Foundation//Tapestry Specification 4.0//EN
http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd;
component-specification class=pt.te.universal.components.login.Login
I think you have left out the delegate attribute in
the Form component.
http://tapestry.apache.org/tapestry4/tapestry/ComponentReference/Form.html
Shing
--- Rui Pacheco [EMAIL PROTECTED] wrote:
Here they go:
This is my .jwc:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE
I am doing exactly as you are and it works just fine for me.
-Original Message-
From: Rui Pacheco [mailto:[EMAIL PROTECTED]
Sent: Monday, July 24, 2006 7:44 AM
To: Tapestry users
Subject: Re: Are components treated as pages?
I am looking at another project where I defined the form
Oops ! What I said about the missing delegate is
rubbish. The validator should work without it. (I have
tested it.)
There should not be any difference whether a
component
is defined explicitly (in jwc or .page) or implicitly
(in .html).
The java class of your component extends
My component extends AbstractBaseComponent. Its a class I created to work as
a parent for all my components. That way I can use inheritance to customize
my components at will.
AbstractBaseComponent itself extends BaseComponent.
On 7/24/06, Shing Hing Man [EMAIL PROTECTED] wrote:
Oops ! What I
I do not know whether the following helps.
In your custom class AbstractBaseComponent, if you
have over ridden any methods of its parent
BaseComponent, please check if you need to do a
super().(overRidden method).
Shing
--- Rui Pacheco [EMAIL PROTECTED] wrote:
My component extends
I didn't override any methods, although calling super could be usefull.
On 7/24/06, Shing Hing Man [EMAIL PROTECTED] wrote:
I do not know whether the following helps.
In your custom class AbstractBaseComponent, if you
have over ridden any methods of its parent
BaseComponent, please check if
Nope, nothing changed.
On 7/24/06, Rui Pacheco [EMAIL PROTECTED] wrote:
I didn't override any methods, although calling super could be usefull.
On 7/24/06, Shing Hing Man [EMAIL PROTECTED] wrote:
I do not know whether the following helps.
In your custom class AbstractBaseComponent, if
To narrow down your problem, you could make the java
class of your component extends BaseComponent directly
(if possible) and
see whether the validator works.
Also, it might be a good idea to post the code of your
AbstractBaseComponent (if it is reasonably short).
Shing
--- Rui Pacheco
I just tried to make my class extend BaseComponent and nothing happened.
This is the source for the base class I use for all my components. Its
pretty straightforward and since all components are DB aware, I handle all
the db logistics in here. But still, I cannot see how this could fail to
I have tested your Login component (in the case
extending BaseComponent and then extending
AbstractBaseComponent) and there is no problem with
the validator.
Shing
--- Rui Pacheco [EMAIL PROTECTED] wrote:
I just tried to make my class extend BaseComponent
and nothing happened.
This is
If I click submit without entering a username and
password, both will be marked by two red asterisks.
Any blank text filed is marked with two asterisks.
I noticed that that in your earlier post,
the .html of the Login component does not have
the form component defined in Login.jwc.
So in my
14 matches
Mail list logo
