I also realized that the advice approach requires a change of ComponentMethodAdvice. That's why I felt comfortable about using the PageActivationContextWorker.
On Sat, Jul 5, 2008 at 12:35 AM, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Igor, > > Earlier I had stated that you should have found a way to use > ComponentMethodAdvice, advising the dispatchComponentEvent() method, > to implement support for the @PageActivationContext annotation. > > I now think I was in error; the ComponentMethodAdvice approach only > works if the advice can be implemented in terms of the public API of > the component, or the method parameters. @PageActivationContext > requires access to the fields of the component. Short of changing > ComponentMethodAdvice to allow access to private fields of the advised > component, it simply is not a good fit. > > > > -- > Howard M. Lewis Ship > > Creator Apache Tapestry and Apache HiveMind > -- Best regards, Igor Drobiazko
