On 10.Jan.2003 -- 09:40 AM, Geoff Howard wrote:
> > From: Christian Haul [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, January 10, 2003 8:56 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: input modules in sitemap component definitions
>
> > > 1) Is it currently possible to use input modules to define the value for
> > > data-source in the action definition example above, where a
> > string value is
> > > returned? (the example in the concepts doc doesn't seem to
> > apply here) What
> > > would the syntax be? Something like <data-source><input-module
> > name="global"
> > > ???="data-source" /></data-source> or something else entirely?
> >
> > No. They can be used wherever 'normal' sitemap variables can be used.
> >
> > Chris.
>
> Thanks for responding -
>
> Bummer. Can you suggest another way to accomplish this or a direction to
> look into patching this?
Not really. So far, all configuration data nested inside a component
declaration is considered private ie the components business.
> The reason I'm wanting to do this is I'm trying to share a mounted sitemap
> from
> others and use a sort of polymorphism - when request comes through sitemap
> A, use
> it's datasource; when it comes through B, use the one named there. As I
> understand
> it, blocks will allow a similar mechanism, so perhaps this would be useful
> then.
It depends on the action. Runtime parameters passed using the
map:parameter syntax are substituted.
If you are using the Cocoon supplied database actions, they accept a
parameter called "connection" for the datasource.
<map:act type="db-add">
<map:parameter name="connection" value="{global:connection}"/>
</map:act>
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
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
