I'd recommend setting the global dependency-check-interval and the jsp
one and not worry about the inheritance aspect. That's what we do and
it works fine.
What you have below should do what you want. The only change I'd make
is to use 60s instead of just 60. I'm not sure if resin assumes
'seconds' or not.
Rob
On Jun 17, 2009, at 01:46, Jens Dueholm Christensen wrote:
Scott Ferguson wrote:
JSP is handled separately and has its own check interval. The
concepts are similar, of course, but the actual needs are different
enough that it made more sense to configure them separately.
Thanks Scott
However, as Rob Lockstone points out regarding the jsp version of
the setting, the default value is inherited – but from where?
If I were to do something like
(Resin 3.0)
<resin>
<dependency-check-interval>-1</dependency-check-interval>
<server>
<host>
<web-app>
<dependency-check-interval>60</dependency-check-interval>
(Resin 3.1/4)
<resin>
<dependency-check-interval>-1</dependency-check-interval>
<cluster>
<host>
<web-app>
<jsp>
<dependency-check-interval>60</dependency-check-interval>
I would still get the behaviour I want (ie. able to change
resin.conf without restart, but still get on-the-fly recompile of
jsp changes), or is the setting for jsp inherited from elsewhere
(and thus the last dependency-check-interval is unnessecary)?
Regards,
Jens Dueholm Christensen
Business Process and Improvement, Rambøll Survey IT
_______________________________________________
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
