Joerg Heinicke pisze: > On 19.09.2007 7:11 Uhr, [EMAIL PROTECTED] wrote: > >> URL: http://svn.apache.org/viewvc?rev=577245&view=rev >> Log: >> COCOON-2134: Implemented Disposable interface in >> StringTemplateParserVariableResolver. > > I wonder why a Spring-configured bean has to implement Avalon interfaces > especially since it is an empty implementation anyway. Wouldn't it be > better to make a instanceof check instead of enforcing the > implementation? Otherwise I don't see how we can get rid of Avalon. We > need such a migration path, don't we?
Thanks for reviewing, you have a good point. The solution I came with was the simplest and most reliable I could think of. After taking another look at the code from o.a.c.components.treeprocessor.variables.VariableResolverFactory class I start to think that we could remove custom managment of Disposable components completely but I will be better to have detailed look into that code later on. -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
