I'm really not a tap 4.x guru, but...
Doesn't it seem funny that id="emailAddress", but the field is
emailAddressComponent?
Now, it may very well be that tapestry 4 will merilly let you have
inconsistent component
ids and method names (like I said, not a tap4 wiz), but, why do you then
also go and define a /String/
property "getEmailAddress", especially when the component is bound to
the person.emailAddress property?
I'd be willing to bet that if you removed the public abstract String
getEmailAddress() line, things would work?
Robert
Ken nashua wrote:
Guys,
All I am trying to do is operate a model object
Person.getEmailAddress() from html to java.
Whats the deal with this notation...
@Component(type = "TextField", id = "emailAddress", bindings = {
"value = ognl:person.emailAddress",
"displayName = message:label.emailAddress", "validators =
required" })
public abstract TextField getEmailAddressComponent();
public abstract String getEmailAddress();
I cannot get past it. it keeps yeilding
[ +/- ] Exception: Component emailAddress conflicts with a prior
declaration in the specification (at Annotation
@org.apache.tapestry.annotations.Component(inheritInformalParameters=false,
type=TextField, bindings=[value = ognl:person.emailAddress,
displayName = message:label.emailAddress, validators = required],
id=emailAddress) of public abstract org.apache.tapestry.form.TextField
proto.Login.getEmailAddress()).
All I want to do is use
<td>
<input jwcid="[EMAIL PROTECTED]" value="ognl:person.emailAddress"
validators="validators:required"
displayName="message:label.emailAddress" />
</td>
If I swap or omit any of the accessor methods it keeps complaining.
Is tap-4.1.1 usable?
Thanks in advance
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
