2009/6/11 Mark Thomas :
> Lyallex wrote:
>> 2009/6/11 Caldarale, Charles R :
>>
>>> Writing to the webapp's deployment location is a bad idea - you again have
>>> no guarantee that it's allowed, and you're at the whims of the container
>>> and execution environment controlling the actual location
Lyallex wrote:
> 2009/6/11 Caldarale, Charles R :
>
>> Writing to the webapp's deployment location is a bad idea - you again have
>> no guarantee that it's allowed, and you're at the whims of the container and
>> execution environment controlling the actual location. Much better to write
>> yo
> From: Lyallex [mailto:lyal...@gmail.com]
> Subject: Re: Dynamic Resources: getRealPath() returns the 'wrong' path
>
> Works perfectly ... except I just cannot get he DefaultServlet to
> serve any images that are written to any directory anywhere on the
> filesystem
2009/6/11 Caldarale, Charles R :
> Writing to the webapp's deployment location is a bad idea - you again have no
> guarantee that it's allowed, and you're at the whims of the container and
> execution environment controlling the actual location. Much better to write
> your files outside of Tom
> From: Lyallex [mailto:lyal...@gmail.com]
> Subject: Dynamic Resources: getRealPath() returns the 'wrong' path
>
> INFO: The path to the image cache is
> C:\servers\tomcat\apache-tomcat-6.0.16\temp\1-ROOT\imagecache
ServletContext.getRealPath() is one of the leftovers from the early days that
p
2009/6/11 Mark Thomas :
> Lyallex wrote:
>> The logging output gives the following
>>
>> INFO: The path to the image cache is
>> C:\servers\tomcat\apache-tomcat-6.0.16\temp\1-ROOT\imagecache
>
> This is a side effect of using the anti-locking attributes on your context.
Er, OK ... thanks.
>
> Mar
Lyallex wrote:
> The logging output gives the following
>
> INFO: The path to the image cache is
> C:\servers\tomcat\apache-tomcat-6.0.16\temp\1-ROOT\imagecache
This is a side effect of using the anti-locking attributes on your context.
Mark
---
