Sorry, I shouldn't have suggested subclassing. The preferred way to extend and/or override a Tapestry component's functionality is to "wrap" it. If you can't achieve what you want with wrapping then maybe create your own component by copying DateField? It might not be much work.
As for your last question, I'll repeat it: "A question to the developers, why isn't tapestry's components events bubbled by default ? Performance issues ?". On 17/12/2012, at 3:13 AM, Muhammad Gelbana wrote: > I should try extedning the datefield component but I have a question, is it > just about my component class "extending" tapestry's component class and > that's it ? No other wiring needed ? > > Just a plain java "extends" and referring to my component instead ? > > A question to the developers, why isn't tapestry's components events > bubbled by default ? Performance issues ? > > On Sun, Dec 16, 2012 at 5:42 AM, Geoff Callender > <geoff.callen...@mac.com>wrote: > >>> This may help: >>> >>> http://localhost:8080/jumpstart/examples/component/eventbubbling >> >> Wrong. I meant this: >> >> >> http://jumpstart.doublenegative.com.au/jumpstart/examples/component/eventbubbling >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
