-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
David Kerber wrote:
> Christopher Schultz wrote:
>> Take a look at in the web.xml: i think you can just put it
>> there and not put anything in server.xml, which would be better, I think.
>>
> Doesn't seem to work - my app isn't finding the
Caldarale, Charles R wrote:
From: David Kerber [mailto:[EMAIL PROTECTED]
Subject: Re: Storing webapp startup parameters
I thought the webapp had to be bounced for this to take
effect, but I'd love to be proven wrong about that!
You're right, it does appear that even a new Init
> From: David Kerber [mailto:[EMAIL PROTECTED]
> Subject: Re: Storing webapp startup parameters
>
> I thought the webapp had to be bounced for this to take
> effect, but I'd love to be proven wrong about that!
You're right, it does appear that even a new InitialContex
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Kerber wrote:
Christopher Schultz wrote:
Aah, okay. That's the same thing as in web.xml, I think.
I think I need to look at that; I'd like to eliminate the entry in
server.xml if possible
Caldarale, Charles R wrote:
From: Christopher Schultz [mailto:[EMAIL PROTECTED]
Subject: Re: Storing webapp startup parameters
A JNDI browser might simplify this for you if you can either deploy it
into your existing application, or if you can somehow connect
to it from the outside
> From: Christopher Schultz [mailto:[EMAIL PROTECTED]
> Subject: Re: Storing webapp startup parameters
>
> A JNDI browser might simplify this for you if you can either deploy it
> into your existing application, or if you can somehow connect
> to it from the outside.
Doesn&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Kerber wrote:
> Christopher Schultz wrote:
>> Aah, okay. That's the same thing as in web.xml, I think.
>>
>>
> I think I need to look at that; I'd like to eliminate the entry in
> server.xml if possible...
Take a look at in the web.x
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
David Kerber wrote:
No, I'm using , with this in server.xml:
This in web.xml:
fileImportInterval
java.lang.string
Aah, okay. That's the same thing as in web.xml, I think.
I th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
David Kerber wrote:
> No, I'm using , with this in server.xml:
>
> value="60"/>
>
> This in web.xml:
>
>fileImportInterval
>java.lang.string
>
Aah, okay. That's the same thing as in web.xml, I think.
> public s
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
David Kerber wrote:
Christopher Schultz wrote:
You could store your preferences in a JNDI context.
If you use in your web.xml instead of using
or something else, then they will be automatically loaded i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
David Kerber wrote:
> Christopher Schultz wrote:
>> You could store your preferences in a JNDI context.
>>
>> If you use in your web.xml instead of using
>> or something else, then they will be automatically loaded into the
>> directory on sta
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Kerber wrote:
Is there a built-in method of having different settings for each
instance of tomcat, but which won't require bouncing tomcat to put the
changes into effect? I know I could roll my own with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David,
David Kerber wrote:
> Is there a built-in method of having different settings for each
> instance of tomcat, but which won't require bouncing tomcat to put the
> changes into effect? I know I could roll my own with a disk file (like
> a window
I know of two built-in methods of storing preferences for a webapp, but
need one with characteristics which combine both of them.
Using the java Preferences class allows changes to be made while the app
is running, but AFAICS they will apply to all instances of tomcat
running on a given machin
14 matches
Mail list logo
