Hmm.. you mean I set my properties once per sitemap run with
System.setProperty(), and it'll remain there?

Christopher

On Thu, Jan 31, 2002 at 09:35:42PM +0100, Jorn Heid wrote:
> I don't know about a Cocoon specific solution but there are many
> possibilities 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 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 space, where I
> could propagate the JNDI settings _once_, and reach from any kind of Cocoon
> class easily? (I said once, cause I dont like the solution of providing it
> as a parameter in the sitemap at each Transformer, Action, etc..)
> 
> thanks much,
> Christopher
> --
> .Digital.Yearning.for.Networked.Assassination.and.Xenocide
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
> 
> 
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
> 

-- 
.Digital.Yearning.for.Networked.Assassination.and.Xenocide

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to