On 25.Jun.2002 -- 11:32 AM, Frank Taffelt wrote:
> > Get yourself default values (from current cocoon.xconf):
> >
> > <component-instance
> class="org.apache.cocoon.components.modules.input.DefaultsMetaModule"
> name="defaults">
> > <input-module name="request"/>
> > <values>
> > <skin>defaultSkin</skin>
> > <base-url>http://localhost:8080/cocoon</base-url>
> > </values>
> > </component-instance>
>
> is it possible to set default values also on a sitemap-level instead to put
> it in cocoon.xconf ?
AFAIK it is possible to declare components in a sitemap using
map:components. Thus
<map:components>
<input-modules logger="core.modules.input">
<component-instance
class="org.apache.cocoon.components.modules.input.DefaultsMetaModule"
name="my-defaults">
<input-module name="request"/>
<values>
<skin>defaultSkin</skin>
<base-url>http://localhost:8080/cocoon</base-url>
</values>
</component-instance>
</input-modules>
</map:components>
would declare a new input module instance accessible with the name
"my-defaults" for this sitemap and all subsitemaps.
I haven't tested this though. But my understanding is, that this is
supposed to work.
There has been a discussion about declaring components in sitemaps a
long time ago and I don't recall the outcome. But I believe it was
decided not to advertise this feature since blocks are likely to
change this.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
