Vjeran Marcinko <vjeran.marcinko <at> email.t-com.hr> writes: > From: "Kent Tong" <kent <at> cpttm.org.mo> > > Your PdfLink component should take a parameter and pass it to > > your service, which will in turn pass to the PdfHandler. This > > will work even in a loop. > > Meaning, anyone who is making such general purpose service/component should > take care to provide way to pass arbitrary number of parameters (such as > DirectLink offers) in some XServiceLink, and offer IRequestCycle argument > inside XServiceProvider interface, so one could fetch parameters by > cycle.getListenerParameters() in it because providing can be dependant upon > various app-specific parameters ?
No. If your XXXServiceProvider should take a Foo object as a parameter, then your XXXService and XXXServiecLink should both take a Foo object as a parameter. > And, "client" persisted property that would get set during each loop turn, > thus generating additional URL parameter to all DirectLinks inside loop > would not function ? I am not sure if I understand what you're saying. A client persistent property will NOT be set in each loop execution. It will be set once for the whole page (or component) after the page is loaded. -- Author of e-book for learning Tapestry (www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
