Vadim Gritsenko wrote:
Grzegorz Kossakowski wrote:
After taking quick look on this problem I saw that JXTemplateGenerator
is broken by the fact that it
implements (indirectly, by extending AbstractXMLProducer) Recycable
interface. Implementing this
interface makes JXTemplateGenerator handled by our Avalon-Spring
bridge instead of pure Spring and
treated as an Avalon component.
Why bridge code is invoked at all for components from spring's
context.xml? Sounds counter intuitive. I would expect only components
from cocoon.xconf/sitemap.xmap would be handled by the bridge code.
I was wondering the same. Maybe Carsten knows more ...
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair [EMAIL PROTECTED]
_________________________________________________________________________
