----- Original Message -----
From: "Kent Tong" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, August 29, 2005 3:13 AM
Subject: Re: The hardest problem ever
Vjeran Marcinko <vjeran.marcinko <at> email.t-com.hr> writes:
It's all nice and easy, but problem is that my page that implements this
interface (provides PdfDocument), is dependant upon some parameter that
was
paseed to it for rendering, but PDF generation is subsequent request and
page doesn't have this parameter anymore.
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 ?
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 ? Because there's no detailed docs about For component,
and about various client peristence strategies, I guess MindBridge would
know this best.
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
