> On 10.Jan.2003 -- 09:40 AM, Geoff Howard wrote:
> > > From: Christian Haul [mailto:[EMAIL PROTECTED]]
> > 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.
Ah, yes - of course. I could choose to interpret the parameter as the name
of the key for an input module, but in that case I'd have to delay lookup
of the datasource until I actually use it (I'm currently setting up a
DataSourceComponent instance variable in configure), which means I might as
well declare the datasource in the pipeline since that functionality would
already be there.
>
> > 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>
I am using those as well (the modular ones) and that'll work. Oh well,
I was trying to do this without modifying my actions, but I guess that
got me off track.
Thanks for the help,
Geoff
---------------------------------------------------------------------
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]>
