On Fri, 8 Feb 2002, DZIEMBOWSKI,KINGA (HP-NewJersey,ex2) wrote:
> In theory yes.
>
> What I like to preserve is the ability to "script" the adapter info. The
> script can be in the sitemap or cocoon.xconf. For the latest I did not see
> the ability to register there multi-item entity. All components registered
> there follow the pattern of one-to-one relationship between role and the
> implementation class. If it is a mechanism to register there multi-item role
> and the configuration - all registration parameters - are available to the
> items through configure() method maybe it is the way to avoid sitemap
> modifications.
Well, I don't know how much Avalon do you know, but Avalon is capable of
much mor than 1-to-1. A Selector allows you to represent roles with
multiple implementations. You should take a look at the cocoon.xconf
file at the bottom. There you should find the following:
<serializers>
<component-instance name="links"
class="org.apache.cocoon.serialization.LinkSerializer"
logger="sitemap.serializer.links"/>
<component-instance name="xml"
class="org.apache.cocoon.serialization.XMLSerializer"
mime-type="text/xml"
logger="sitemap.serializer.xml"/>
<component-instance name="html"
class="org.apache.cocoon.serialization.HTMLSerializer"
mime-type="text/html"
logger="sitemap.serializer.html"
pool-max="32" pool-min="4" pool-grow="4">
<buffer-size>1024</buffer-size>
</component-instance>
</serializers>
Does remind you of something? Do you see that the serializer role will
have several different implementations? Does such a capability solve
your problems?
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
