I have a global input module defined in map:component-configurations (2.1):
a-string
...
Currently, I'm using values defined this way later in the sitemap with
{global:XXX} and in xsp's with the input logicsheet (works great).
I would like to use it to define the datasource defin
> 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
> declaratio
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 curren
> -Original Message-
> 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 t
On 10.Jan.2003 -- 08:42 AM, Geoff Howard wrote:
> I have a global input module defined in map:component-configurations (2.1):
>
>
>
>
> a-string
>
> ...
>
> Currently, I'm using values defined this way later in the sitemap with
> {global:XXX} and in xsp's with the input logicsheet
I have a global input module defined in map:component-configurations (2.1):
a-string
...
Currently, I'm using values defined this way later in the sitemap with
{global:XXX} and in xsp's with the input logicsheet (works great).
I would like to use it to define the datasource defin
