Hmm, sorry, I don't really understand what you want to achieve. The snippet you're refering to is for the configuration of a (single) coplet data/instance.
All these objects (coplet data, coplet instance data and coplet base data) are just *data* objects - which means they are holding data (state) but do not contain any logic. The logic for coplets resides in the coplet adapters in the coplet implementations (pipelines, JSR 168 etc.), so I think if you want to implement some pooling, you can do it in your own adapter. HTH Carsten Jean-Christophe Kermagoret wrote: > Hello, > Is there in the portal a way to create coplet instances in advance, to > reduce the first connection overhead ? A kind of coplet instance pool > that could be configured by profile ? > > By the way, I saw in 2.1.8 the following configuration snippet in > cocoon.xconf, with coplet-factory, 'auto-create' and store attributes > that sound like keywords for me :-) > > What is it for ? > > <component > class="org.apache.cocoon.portal.coplet.impl.DefaultCopletFactory" > role="org.apache.cocoon.portal.coplet.CopletFactory"> > > <coplets> > <coplet > class="org.apache.cocoon.portal.coplet.CopletData" > name="standard"> > > <coplet-data-aspects> > <aspect > auto-create="true" class="java.lang.Boolean" > name="sizable" store="memory" value="true"/> > <aspect > auto-create="true" class="java.lang.Boolean" > name="mandatory" store="memory" value="false"/> > </coplet-data-aspects> > > <coplet-instance-data-aspects> > <aspect > auto-create="true" class="java.lang.Integer" > name="size" store="session" value="1"/> > <aspect > auto-create="true" class="java.lang.Boolean" > name="fullScreen" store="temporary" value="false"/> > </coplet-instance-data-aspects> > </coplet> > </coplets> > </component> > > Jean-Christophe -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
