On 27/07/2011 17:06, David Wolverton wrote:
> Thanks Ognjen,
>
> Using 'reloadable' does cause the resources to update. However, this is not
> the solution I am looking for because it does this by reloading the webapp.
> It can take a lot of time for the webapp to restart and cause other side
> ef
On 28/07/2011 08:31, Pid wrote:
> On 27/07/2011 17:06, David Wolverton wrote:
>> Thanks Ognjen,
>>
>> Using 'reloadable' does cause the resources to update. However, this is not
>> the solution I am looking for because it does this by reloading the webapp.
>
> The classloader initialises at loadti
On 27/07/2011 17:06, David Wolverton wrote:
> Thanks Ognjen,
>
> Using 'reloadable' does cause the resources to update. However, this is not
> the solution I am looking for because it does this by reloading the webapp.
The classloader initialises at loadtime, in order to release resources
and loa
Thanks Ognjen,
Using 'reloadable' does cause the resources to update. However, this is not
the solution I am looking for because it does this by reloading the webapp.
It can take a lot of time for the webapp to restart and cause other side
effects, so I would prefer not to have to do this.
Anyone
Hi David,
On 27.7.2011 16:20, David Wolverton wrote:
I'm running Tomcat 7.0.19 with IntelliJ IDEA IDE. I'm using the new Servlet
3.0 feature that allows webapp resources to be served from within JARs'
META-INF/resources directory. This technique is working fine, however I
would like to be able t
