On 12/22/2014 8:14 AM, Kevin McKee wrote:
For anyone else unable to find an answer to this problem, the answer seems
to be as simple as adding this to your $SERVER_HOME/conf/context.xml
inside the <Context> tag
<Resources cachingAllowed="false"/>
As long as you don't need caching...
Kevin McKee
Application Development Architect
Goodyear Canada Inc.
388 Goodyear Rd, Napanee, ON K7R 3L2
phone.613.354.7850
krmc...@goodyear.com
On 2014-12-16, 7:21 PM, "Christopher Schultz"
<ch...@christopherschultz.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Kevin,
On 12/12/14 4:10 PM, Kevin McKee wrote:
I have read the reference, but nowhere can I find an example of
what it’s talking about.
Not counting titles, headings, and the TOC, they are sentences #6 and
#7 on the page, starting from 1.
"
A Resources element MAY be nested inside a Context component. If it is
not included, a default filesystem based Resources will be created
automatically, which is sufficient for most requirements.
"
My web.xml / context.xml don’t have a resource component in it
that I can find, and nowhere can I find out what the syntax is or
where to put it.
"
If it is not included, a default filesystem based Resources will be
created automatically, which is sufficient for most requirements.
"
So, your <Context> element does not already have a <Resources> element
because a) you wrote it yourself and b) you never noticed because "a
default filesystem based Resources" was created "automatically, which
is sufficient for most requirements."
Since you are stepping outside those requirements, it's time to define
your own <Resources> element.
This is why I’ve reached out to this group for help. If you can
point me to an example or more detailed info I would appreciate
it.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJUkIZKAAoJEBzwKT+lPKRY15IQAJqWotAkdWLm6tcg1UKfFSzK
zs5Mypz3ROfEVO2akeZl+BJ04oac4detZ9cZMKrqlyJsaVod8l5tIOCbX1EuLP/l
MllgrtWlshO4wnrzHhQsRkLQ2KwV8SlIe8FR08P2WlHBeoCAXa32vuWbC9maalfY
8U75Kx8/PXAk3/WlmTXNsx9TFuylNXtJLoYKKSdRV4MRL8A54n9KOylebSlxOnEI
JYVbarf5et33fXCXJewCmMQzlv1Nq74Po5rlQ2zP1ltIJhITduvieWPa/+OIdBBJ
3oFyl6s/6blcfeaJ73fQI4M4eEBFHVbB1jBUHENqrCSETTvzn22s49TVsg6wrjLX
cN/U/XyXFZWtcFhzUzp4EcJdirAsQ1r1M1SKbGQZux6nkELaV3/OKTrn98RyXNMQ
qhKTlEc0OKGR7pXQE0Gmacue+i4WMQiigXSDwPp1XXSlRSsqb6/LGo8l6aCQiqer
q6rcIY6BBUkwQprMZFt7eTmlyWb13ue4IFDB7qEySCeP25T9XealATpLDYmmMiXx
ISCgtokb85o0b6hPYApxX0iNzySFMiTWQvG6dCEsPrwfgQsmE+F0ftG/sVizVEUN
/PIzfuinNaFz5NCCB/qSEEuDLIraPs3XEJugA5v4LX/Iq09ADjUTfilxtjD0mwtt
BGEnU/8swDbeQQEzdIgK
=zRiu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
