It sounds like you might be better off writing your own "ajaxlink" component that always does xhr? You can certainly still tie into Tapestry's ajax/zone handling, and asking tapestry to generate the links is simple.
Robert On Nov 5, 2011, at 11/56:42 AM , 9902468 wrote: > Hi, > > I get that error, if I use the ajaxResponseRenderer service during the > handling of an event, that has originated from a link that does not have > it's zone set. I understand the technical reason for this. > > We have a fairly complex system, and we do not know beforehand what zones > the page contains in which we have to use our componentized links. To > circumvent this we currently have one global zone that is always in the page > (main layout template), but this solution is not very elegant. > > So, can we mark actionlink as "just do xhr request" without giving it the > zone? Should this be similar "magic" marker as the ^? > > - Ville > Ps. The error message could be more descriptive too "You are trying to reply > with ajax to non-ajax request" or similar and then track the originating > link + the point in code that calls the ajaxresponserenderer. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Tapestry-5-3-rc3-Page-must-be-specified-before-initializing-for-partial-page-render-tp4966505p4966505.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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
