cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <>
Subject Re: Problems with writing sitemap components as spring beans
Date Thu, 04 Jan 2007 11:17:09 GMT
Daniel Fagerstrom wrote:
> After having looked at I think that the simplest solution would be to 
> just provide one (singleton) info bean for each component. Something like:
>   <util:map name="org.apache.cocoon.serialization.Serializer/xml/info">
>     <entry key="mime-type" value="text/xml"/>
>     <entry key="label" value="output"/>
>   </util:map>
>   <bean name="org.apache.cocoon.serialization.Serializer/xml" 
> class="org.apache.cocoon.serialization.XMLSerializer"
>         scope="prototype" 
> parent="org.apache.cocoon.serialization.AbstractTextSerializer"/>
> Then the ProcessorComponentInfo can just look up the info from the 
> container using <ComponentType>.ROLE/<hint>/info as key.
> If it is better to store the info in the ProcessorComponentInfo, we 
> could have a bean factory that looks up the ProcessorComponentInfo (or 
> create it if needed), and store the info there instead:
>   <bean name="org.apache.cocoon.serialization.Serializer/xml/info"
> class="org.apache.cocoon.core.apropriate_sub_package.ProcessorComponentInfoBeanFactory">
>     <property name="mimeType" value="text/xml"/>
>     <property name="label" value="output"/>
>    </bean/>
> In this case the bean name is parsed for finding out what sitemap the 
> component info is about. We could combine any of the above solutions 
> with a custom xml format if we like to get a "prettier"notation.
I think the first solution is the a little bit easier to implement and
does not require to much coding in xml for the configuration, so I think
we should go for the first solution.

If anyone has time to imlement it, we could think about adding our own
tags for this configuration, so this could look like this:
<bean name="org.apache.cocoon.serialization.Serializer/xml"
  <namespace:sitemap-component label="gg" mime-type="..."/>

This shouldn't be too hard.

> Whatever solution we use, the mechanism for being able to store the info 
> must be part of the pipeline layer, so that we can configure the 
> pipeline components there.
Yes, it would be good if we could move this stuff out of the current
avalon bridge!


Carsten Ziegeler - Chief Architect

View raw message