In case it's of use to someone at some stage, the reason my decorateClientInfrastructure method wasn't being called as it was trying to decorate an already decorated service (due to testing tapestry5-jquery), as suggested in http://tapestry.markmail.org/message/a3ocq7gmu4iirg22?q=decorate - hard to find duplicates in third party libraries sometimes. Reordering the JS files using a custom client infrastructure to put the jquery related ones before prototype did the trick for IE8 (+compatibility mode), and had no negative impact in Firefox. This is just under Tap 5.2.0-SNAPSHOT - didn't notice any issues with Tap 5.1.0.5 (prototype 1.6.0.3).
Regards, Jim. -----Original Message----- From: Jim O'Callaghan [mailto:[email protected]] Sent: 26 May 2010 12:02 To: 'Tapestry users' Subject: Tap 5.2.0-SNAPSHOT Javascript file inclusion order I'm working through an upgrade to Tap 5.2.0-SNAPSHOT at the moment and having some issues would really appreciate any pointers on. Prototype 1.6.1 (supplied with Tap 5.2.0-SNAPSHOT) doesn't appear to play nice with jQuery (IE 8 only), effectively breaking client-side validation - I'm thinking it down to the order of JS script inclusions (as suggested here: http://tapestry.markmail.org/message/meemcpo6spv2f6cr?q=clientinfrastructure ). I'm using jQuery, with noConflict set, but my JS file inclusion order is: prototype.js scriptaculous.js effects.js tapestry.js blackbird.js tapestry-messages.js utils.js jquery-1.3.2.min.js jquery-ui-1.7.1.custom.min.js common.js In my common Layout.tml I have: @IncludeJavaScriptLibrary({"context:/scripts/utils.js", "context:/scripts/jquery-1.3.2.min.js", "context:/scripts/jquery-ui-1.7.1.custom.min.js", "context:/scripts/common.js"}) Is it the jump from prototype 1.6.0.3 (w/ T5.1.0.5) to prototype 1.6.1 (w/ T 5.2.0) that is causing an issue? On a related note I'm also finding a decorate method I used to use in my AppModule is no longer being called: public ClientInfrastructure decorateClientInfrastructure(ClientInfrastructure original, @InjectService("AssetSource") AssetSource assetSource) { . . . } ... which is causing other new behaviour. Are there any docs / notes on the jump from 5.1.0.5 to 5.2.0-SNAPSHOT relating to this area? Regards, Jim. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
