Cool, I'll try this myself - for I'm also source patching the same DateField bug (TAP5-841) in multiple projects. It just hadn't annoyed me enough to look for a solution!
I also like the idea of a 302 for mis-versioned assets - nice thinking! Steve. ------------------------------- "If at first you don't succeed, so much for skydiving!" On 23 February 2012 08:16, Paul Stanton <p...@mapshed.com.au> wrote: > Thanks Thiago, > > I managed it by decorating ComponentInstantiatorSource and overriding > DateFieldStack. > > No patched jar required now! > > > On 22/02/2012 8:50 PM, Thiago H. de Paula Figueiredo wrote: >> >> On Tue, 21 Feb 2012 22:55:30 -0200, Paul Stanton <p...@mapshed.com.au> >> wrote: >> >>> Hi Thiago, >> >> >> Hi, Paul! >> >>> I'd love to not have to patch but how can I override the DateField >>> component (java & js) via tapestry-ioc? >> >> >> Decorate or advise or override ComponentClassResolver so its >> resolveComponentTypeToClassName() method returns your DateField class name >> instead of the one provided by Tapestry. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
