On Fri, 27 Jun 2014 02:01:29 -0300, Claude Andrew
wrote:
d'oh. I fixed it myself. It turns out that setting the app.properties
setting
tapestry.production-mode = false
did not work but the following did:
That's the expected behavior. Symbol values aren't looked up from
app.properti
Thanks! Exactly what I was looking for.
On Fri, Jun 27, 2014 at 6:30 PM, Dmitry Gusev
wrote:
>
> http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/ReloadAware.html
>
> On Friday, June 27, 2014, Ilya Obshadko wrote:
>
> > I have a couple of services which use PeriodicExecutor to p
It's a proxied service and the only one persisted. The debugger I mentioned
before is XRebel, and it shows that the stored service holds a reference to
both a token (ServiceProxyToken) and a creator (JustInTimeObjectCreator).
The main issue here seems to be that the latter references
registryShutdo
http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/ioc/ReloadAware.html
On Friday, June 27, 2014, Ilya Obshadko wrote:
> I have a couple of services which use PeriodicExecutor to perform
> background tasks.
>
> When service implementation reloads in development mode, instantiated
> back
I have a couple of services which use PeriodicExecutor to perform
background tasks.
When service implementation reloads in development mode, instantiated
background job isn't stopped. So, after implementation is reloaded, it
creates another background jobs while previous one still exists and
conti
