You don't have to be a 4.x expert to recognize this one; I told you
before. :)
You're trying to implicitly and explicitly define the same component,
and tapestry is complaining.
There are two types of component definitions in tapestry: explicit, and
implicit.
Implicit definitions define the entire component in the template.
Explicit definitions define all or part
of the component in either the spec, or via annotations. If you have
defined a component with the id of "emailAddress"
either in your .page/.jwc or in the .java file via annotations, you
CANNOT do:
<input jwcid="[EMAIL PROTECTED]".../>
^^^^^^^^
It's the "@TextField" part that's making tapestry complain. Putting:
<input jwcid="emailAddress"/> is saying: use a component with the id of
emailAddress which I defined elsewhere
(ie, .page/.jwc or via annotations). Putting:
<input jwcid="[EMAIL PROTECTED]"> is saying:
create a new component with the id of "emailAddress" and type
"TextField". Since you've already defined
"emailAddress" (via annotations at first and more recently via the .page
spec), tapestry complains. That's what the:
"Component emailAddress conflicts with a prior declaration in the
specification (at context:/WEB-INF/Login.page, line 5, column51)."
is telling you. (If you look, this is the same exception you were
receiving when you specified the component via annotations).
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
