Good news! I had to face the same problem with some tapestry5-jquery components Your issue is related to TAP5-2463. This should be fix in next version.
Anyway, if you don't have any legacy code that use prototype.js, it is better to only use jQuery. Best regards François 2015-09-13 17:46 GMT+02:00 Christine <myli...@christine.nl>: > On 13-09-15 11:12, françois facon wrote: > >> Hi Christine, >> >> Did you try to force the use of jQuery whithout prototype in your beta35 >> version ? >> >> This could be done by adding the following code configuration.add( >> SymbolConstants.JAVASCRIPT_INFRASTRUCTURE_PROVIDER, "jquery"); >> in the contributeApplicationDefaults part of your AppModule. >> > > that worked, thank you. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
