Hi! Yes, in someway, it should be possible to change the automatically included JS when extending a component. Already encountred this problem too. Had to create and advice/decorator on asset source to fix the thing without forking the component.
On Sat, Mar 6, 2010 at 4:39 AM, Joost Schouten (ml) <joost...@jsportal.com>wrote: > Hi, > > I have found another problem when extending the Autocomplete Mixin which > has been introduced by recent changes on the 5.2.0-SNAPSHOT version. > > - The @Override methods (eg. generateResponseMarkup(MarkupWriter writer, > List matches)) are no longer called on the extending class > > On the dev list I have already raised the following: > - The mixin will try to load the autocomplete.js from the classpath > location of the extending class, in stead of the Autocomplete.class > > I have submitted a bug in jira [1] for this. Please let me know if I am > mistaken and have previously used the mixin inappropriately. > > Cheers, > Joost > > [1]: https://issues.apache.org/jira/browse/TAP5-1047 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
