Molnar Peter pisze:
On Ked, Július 22, 2008 2:12 pm, Grzegorz Kossakowski wrote:
We have a Avalon-Spring bridge that will pick up all Avalon components and
initialize them using
Spring so in a fact they are Spring beans.
That was made on purpose to make a transition from Avalon to Spring
smooth.
Does this mean, that if my sitemap component (reader) is a purely spring bean
(it accesses only resources from the spring context), I can omit avalon
lifecycle interfaces?
Even better. You can implement any of Cocoon components as pure Spring beans, with Spring
configuration and dependency injection.
The template generator and template block itself is a good example of such way of defining sitemap
components, see:
http://svn.eu.apache.org/viewvc/cocoon/trunk/blocks/cocoon-template/cocoon-template-impl/src/main/java/org/apache/cocoon/template/JXTemplateGenerator.java?view=markup
http://svn.eu.apache.org/viewvc/cocoon/trunk/blocks/cocoon-template/cocoon-template-impl/src/main/resources/META-INF/cocoon/spring/cocoon-template.xml?view=markup
--
Best regards,
Grzegorz Kossakowski
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
