cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: Restructuring directory structure[was [Vote] Block artifact directory structure]
Date Sun, 05 Nov 2006 15:01:03 GMT
Giacomo Pati wrote:
> 
> Leszek Gawron wrote:
>> Giacomo Pati wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>>
>>>
>>> Leszek Gawron wrote:
>>>> Giacomo Pati wrote:
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>>
>>>>>
>>>>> Carsten Ziegeler wrote:
>>>>>> Leszek Gawron wrote
>>>>>>> I doubt that is possible in spring. Probably the class of bean
>>>>>>> definition must be known even before BeanFactoryPostProcessors
apply.
>>>>>> Yes, it's not possible this way. Spring reads in the configuration,
>>>>>> creates the
>>>>>> bean definition object, does some class checking on the beans (for
>>>>>> example if the bean implements some bean processing interfaces) and
>>>>>> then
>>>>>> applies the properties.
>>>>>>
>>>>>> Our own version we had before was reading in the XML itself and
>>>>>> applying
>>>>>> the properties during reading the XML. So if we would need the same
>>>>>> behaviour again we have to give our own XML reader/parser to Spring
>>>>>> (which might be possible).
>>>>> No need for anymore. Leszek showed me the way to do what I wanted.
>>>> This currently works if you place files in
>>>> classpath:/META-INF/cocoon/spring and
>>>> classpath:/META-INF/cocoon/spring/mode
>>> Sure.
>>>
>>>> it's a little bit too complicated for me to make this for for
>>>> block/config/spring and block/config/spring/mode
>>> Wa's this? dDo we have a config directory somewhere as well?????
>> When you put spring context into classpath:/META-INF/cocoon/spring you
>> actually contribute spring beans directly to core. They are in the same
>> context as cocoon internals.
>>
>> If you want some beans to be sitemap specific put your spring context
>> files into block/COB-INF/config/spring (analogous for properties
>> block/COB-INF/config/properties). The context files residing there will
>> create a separate child spring context.
>>
>> Same goes for legacy components: block/COB-INF/config/avalon (instead of
>> declaring them in sitemap.xmap/map:sitemap/map:components)
> 
> Hmm.. I think someone knowledgeable need to write all those directory
> possibilities down somewhere if it is not already.
> 
> Are those config/{avalon,spring} directories {mode} aware as well?

no not yet. We need to come up with the solution we are discussing in 
other thread (System.getProperty() vs Settings.getRunningMode())

-- 
Leszek Gawron                                    CTO at MobileBox Ltd.


Mime
View raw message