Ok, so rarely you need to roll your own IRequestTargetUrlCodingStrategy, we do provide implementations to cover most common cases. And even if you do, you only need to know about IRequestTarget - which has good javadoc, and so does the coding strategy. You dont need to know anything about the irequestcycleprocessor, in fact it might even go away at a later release.
-igor On Jan 12, 2008 11:56 AM, Dmitry Kandalov <[EMAIL PROTECTED]> wrote: > On Saturday 12 January 2008 23:25:43 Igor Vaynberg wrote: > > sure, and all you need to know is that you subclass > > requestcycle.onbeginrequest() and add your own code there and it is > > called at the beginning of the request. why do you need to know the > > sequence of calls that leads to onbeginrequest() being called? > > I don't. I can image someone may want to be sure that this method is called > before anything else he overrides, or to know that he can't get requested > page at this step, but probably it's a very rare case. > > Though creating things like IRequestTargetUrlCodingStrategy requires knowledge > about targets and request processor. > > On the whole I think it's the matter of knowing the big picture and not using > framework as a black box. I don't mean everyone should do it. > > > > Dima > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
