On Fri, 8 Feb 2002, DZIEMBOWSKI,KINGA (HP-NewJersey,ex2) wrote: > > -----Original Message----- > > From: giacomo [mailto:[EMAIL PROTECTED]] > > Sent: Friday, February 08, 2002 3:02 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: Dispatcher/Adapter > > > > > > 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? > > I do not have the doubts that multicomponents roles exists for Avalon > components! > All sitemap components are in this category including my adapter and this is > my point. > > The syntax you are showing satisfy me in 100%. I do understand that sitemap > components registered in cocoon.xconf have this same "treatement" that those > registered in the sitemap.xmap. > > Just for curiosity why some sitemap components are registered in the sitemap > and some in cocoon.xconf. What is the criteria used to make the decision > where to register the component?
To tell you the truth: I DON'T KNOW! they shouldn't be there (or I've missed some changes recently). There has beeen proposals to move all component from the sitemap.xmap to the cocoon.xconf but we have not come to a decision. So, Vadim, why are they there? Giacomo > > Kinga > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
