I don't know if this qualifies as a bug, I think not ... having a service call one of its own methods via its proxy is not unreasonable (and should be supported) BUT would not be the normal case and would need to see a use case for it (which is why I really like interfaces with just one method :-)
What are you actually trying to accomplish, perhaps there is another way? On Wed, Jan 6, 2010 at 9:41 AM, cordenier christophe <christophe.corden...@gmail.com> wrote: > Hi, > > I am facing a problem related to the design of FieldTranslatorSourceImpl > internal class design. > > I would like to adivse one of the method to pass my own modified instance of > Translator, but actually the adivor does'nt work for this method because the > public method (from the interface) is called from the inside... and the one > invoced by the Tapestry other internals is not the one i wan't to decorate > of course :) > > Is this a bug or a design principal to secure internal classes ? > > Best Regards, > Christophe. > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
