Other systems create a subclass of the class, to act as a proxy, and then override all the public methods of the proxy. This is haphazard at best, which is why Tapestry has (to date) avoided it. However, there's no reason why Tapestry IoC could not accomplish the same thing, it's just been a choice not to do so ... to have pure services (with an interface) have the full feature set (live reloading, late instantiation, proxies, decorators, advice) and have impure services (just an implementation) get minimal support (injection).
On Wed, Feb 15, 2012 at 8:42 AM, Denis Stepanov <[email protected]> wrote: > Hello, > > Is there a way how circular dependencies of non-interface instances could be > supported by Tapestry IOC? > > It seems that a service without an interface is not proxied and it leads to > the stack overflow(https://issues.apache.org/jira/browse/TAP5-1772), I know > that Hibernate can create a proxy without an interface so it should't be a > problem. Spring doesn't have a problem with circular dependencies, I'm > converting Spring code to Tapestry IOC and I'm surprised Tapestry cannot > handle it. > > Denis > > -- 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: [email protected] For additional commands, e-mail: [email protected]
