Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.
The following page has been changed by JesseKuhnert: http://wiki.apache.org/jakarta-tapestry/41RenderCycleDesign ------------------------------------------------------------------------------ <item value="proj3">Project 3</item> </select> </response-element> + <response-element id="scriptblock"> + dojo.event.connect(dojo.byId("projectSelect"), "onchange", function() { + dojo.io.bind({ url: "http://localhost:8080/app?service=direct&component=projectSelect&listener=selectProject", + load:function(data) { + //do something with returned data here + } + }); + </script> + </response-element> </xml> }}} + + As you can see, all of the same issues/solutions put in place for html content have to be similarly applied to javascript content. If you allowed the Body component to render the javascript block for a typical response you would get an extroidinary amount of script back in your response that had nothing to do with the components you were trying to refresh. A new interface needs to be added in that will allow similar "filtering" to occurr with javascript blocks, on a per component basis, as with normal html content. ==== What's happening on the server? ==== In it's most basic form, tapestry as a whole generally does the following. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
