Yes, to avoid the class. 4.0 lets you override which attribute to look for, so you can use id instead of jwcid (but then you can't set the id of your rendered elements).
On 5/10/05, Karthik Abram <[EMAIL PROTECTED]> wrote: > > Won't the id field clash with html ID?? > > -----Original Message----- > From: Gregg D Bolinger [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 10, 2005 5:48 PM > To: Tapestry users > Subject: Curiosity Question > > Why does Tapesty use jwcid= instead of just looking for the id attribute and > then verfying that against the .page specification as it does for the jwcid. > Would it be harder to catch missing components early on? Just curious. > > Gregg Bolinger > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
