Hi, just noticed that the following does not work and it bugs me since I
don't know how the dev is up-to-date...
{/name_of_my_global_parameter} is empty.
Babs
---
>From Vadim in last May :
One thing left - to add {/paramname} syntax...
Hint-hint ;)
Vadim
--
I really wonder why they're so buggy to use... I have to have
../../ }-like path to access them, and they seem not to be as
path-logically accessible as the ordinary parameters, at least I have
troubles with them.
Just my two hot cents :-(
I will have a look at the other solution (definition in
Hi Chris, nope, I have to use the "right path"... and have troubles with
level 6.
So...
Barbara
- Original Message -
From: "Christian Haul" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 06, 2002 8:39 AM
Subject: Re: global-parameter
On 05.Sep.2002 -- 06:25 PM, Barbara Post wrote:
> Hello, evening here...
>
> In c2.1, do the global parameters respect the stack created by actions ?
>
> So, if I have pipeline 1 and 3 nested actions in it, in the latest one I
> want to access "foo1" global-parame
I change a pipeline, go to the url in the browser, and it keeps failing
although the levels' depth is correct. Either the pipeline's execution fails
or it says "no such level". I feel bugged. Thanks for any other feedback
about this.
Some pipeline perfectly work. Maybe I have to restart cocoon ?
Hello, evening here...
In c2.1, do the global parameters respect the stack created by actions ?
So, if I have pipeline 1 and 3 nested actions in it, in the latest one I
want to access "foo1" global-parameter, do I use {../../../foo1} ?
In pipeline 2, with one action, {../foo1} ?
Tha
224924482&r=1&w=2
Which resulted in implementation of 'global-parameters' for a pipeline.
Thanks to Carsten.
Konstantin
>
> Geoff Howard
>
>
> -Original Message-
> From: Eduardo Godoy [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 28, 2002 12:49 PM
, 2002 9:56 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Global parameters
I believe that there is currently no way to do this, but there happened
to
be a similar proposal recently on the dev mailing list. You should be
able
to find the discussion here:
http://marc.theaimsgroup.com/?t=1022492
Eduardo Godoy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 28, 2002 12:49 PM
To: [EMAIL PROTECTED]
Subject: Global parameters
Hi Folks,
I'd like to know how to define a "global" parameter for all my pipeline
...
for example... the "Soap Host name" ... this parameter
is is not the best way to define the
global parameters ... any idea? or something to read ?
Thanks
Eduardo.
Hi,
Cocoon2 offers a sample ParentComponentManager, for accessing JNDI
see documentation developing/parent-component-manger.html.
It explains integrating JNDI accesss.
Perhaps it helps you.
bye bernhard
-
Please check that y
achricht-
> > Von: Jozsa Kristof [mailto:[EMAIL PROTECTED]]
> > Gesendet: Donnerstag, 31. Januar 2002 21:25
> > An: [EMAIL PROTECTED]
> > Betreff: Where to place global parameters..?
> >
> >
> > Hi,
> >
> > the subject may not be accurate. I&#x
ities to do this:
>
> System.getProperty()
> Static class
> Application attributes (s. Servlet documentation)
>
> -Ursprungliche Nachricht-
> Von: Jozsa Kristof [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 31. Januar 2002 21:25
> An: [EMAIL PROTECTED]
> Betreff: Where to p
02 21:25
An: [EMAIL PROTECTED]
Betreff: Where to place global parameters..?
Hi,
the subject may not be accurate. I'm using Cocoon in an EJB environment, and
I have to use some parameters, like JNDI settings from most of my own
Transformers, Selectors, Actions, and so. Is there any global sp
Hi,
the subject may not be accurate. I'm using Cocoon in an EJB environment, and
I have to use some parameters, like JNDI settings from most of my own
Transformers, Selectors, Actions, and so. Is there any global space, where I
could propagate the JNDI settings _once_, and reach from any kind of
15 matches
Mail list logo
