You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Joerg Heinicke <jo...@gmx.de> on 2007/08/16 05:42:53 UTC
Cocoon Spring configurator
Carsten Ziegeler <cziegeler <at> apache.org> writes:
> Ah, great, yes bean map has been added later - I'll document it in the
> next days.
Carsten, when I recommended the bean map today [1] I wondered how it actually
works. The documentation talks about jar drop-in [2] which does not seem to be
the full truth. Please correct me if I'm wrong ...
The BeanMap looks for all beans of a particular type. Therefore the beans needs
to be registered in the application context. So far so good, but here I think
the drop-in fails. Even if the jar includes the configuration the bean does not
get added automatically to the application context. Only the other parts of
Cocoon Spring configurator enable this functionality. (If that's correct this
should better be added to the BeanMap documentation.) Which class exactly does
this? And how much stuff is hard-coded in it? You don't want to have paths like
/META-INF/cocoon/spring when using Cocoon Spring configurator independently from
Cocoon. It's probably not that hard to change but we should do it before
propagating it :)
Regards,
Joerg
[1] http://forum.springframework.org/showthread.php?t=42701
[2] http://cocoon.zones.apache.org/daisy/cdocs-spring-configurator/g1/1400.html
Re: Cocoon Spring configurator
Posted by Carsten Ziegeler <cz...@apache.org>.
Reinhard Poetz wrote:
> Carsten Ziegeler wrote:
>>> /META-INF/cocoon/spring when using Cocoon Spring configurator
>>> independently from
>>> Cocoon. It's probably not that hard to change but we should do it before
>>> propagating it :)
>> There are constants defined in
>> org.apache.cocoon.spring.configurator.impl.Constants.
>>
>> So changing this is very simple. The whole loading is done through own
>> xml elements (the "settings" element). Most classes in
>> org.apache.cocoon.spring.configurator.impl deals with this stuff.
>
> That means that we can make this a configuration option of the settings
> element and its default value is "META-INF/cocoon/spring", right?
The best thing is that we already have this :)
you can embed "include-beans" and "include-properties" in the settings
element which allow you to read the configuration from additional locations.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Cocoon Spring configurator
Posted by Joerg Heinicke <jo...@gmx.de>.
On 19.08.2007 11:56 Uhr, Reinhard Poetz wrote:
>>> /META-INF/cocoon/spring when using Cocoon Spring configurator
>>> independently from Cocoon.
>>> It's probably not that hard to change but we should do it before
>>> propagating it :)
>>
>> There are constants defined in
>> org.apache.cocoon.spring.configurator.impl.Constants.
>>
>> So changing this is very simple. The whole loading is done through own
>> xml elements (the "settings" element). Most classes in
>> org.apache.cocoon.spring.configurator.impl deals with this stuff.
>
> That means that we can make this a configuration option of the settings
> element and its default value is "META-INF/cocoon/spring", right?
That's what I understood.
Joerg
Re: Cocoon Spring configurator
Posted by Reinhard Poetz <re...@apache.org>.
Carsten Ziegeler wrote:
>> /META-INF/cocoon/spring when using Cocoon Spring configurator independently from
>> Cocoon. It's probably not that hard to change but we should do it before
>> propagating it :)
> There are constants defined in
> org.apache.cocoon.spring.configurator.impl.Constants.
>
> So changing this is very simple. The whole loading is done through own
> xml elements (the "settings" element). Most classes in
> org.apache.cocoon.spring.configurator.impl deals with this stuff.
That means that we can make this a configuration option of the settings element
and its default value is "META-INF/cocoon/spring", right?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: Cocoon Spring configurator
Posted by Carsten Ziegeler <cz...@apache.org>.
Joerg Heinicke wrote:
> Carsten Ziegeler <cziegeler <at> apache.org> writes:
>
> Carsten, when I recommended the bean map today [1] I wondered how it actually
> works. The documentation talks about jar drop-in [2] which does not seem to be
> the full truth. Please correct me if I'm wrong ...
:)
>
> The BeanMap looks for all beans of a particular type. Therefore the beans needs
> to be registered in the application context.
Yes, that's true - so you can use the bean map "standalone" without
using anything else from the configurator.
> So far so good, but here I think
> the drop-in fails. Even if the jar includes the configuration the bean does not
> get added automatically to the application context. Only the other parts of
> Cocoon Spring configurator enable this functionality. (If that's correct this
> should better be added to the BeanMap documentation.)
Yes, that's true - the bean map is just a map of some registered beans.
Together with the other functionality of the spring configurator you get
the automatic configuration stuff - and if such a configuration
contains beans for the map, they are added to the map of course.
Yepp, I think this needs some clarifications in the docs.
> Which class exactly does
> this? And how much stuff is hard-coded in it? You don't want to have paths like
> /META-INF/cocoon/spring when using Cocoon Spring configurator independently from
> Cocoon. It's probably not that hard to change but we should do it before
> propagating it :)
There are constants defined in
org.apache.cocoon.spring.configurator.impl.Constants.
So changing this is very simple. The whole loading is done through own
xml elements (the "settings" element). Most classes in
org.apache.cocoon.spring.configurator.impl deals with this stuff.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org