I don't use GAE, but this might help:
@Contribute(ServiceOverride.class)
public static void
createNOOPPeriodicExecutor(MappedConfiguration<Class, Object>
configuration) {
configuration.add(PeriodicExecutor.class, new PeriodicExecutor() {
@Override
public PeriodicJob addJob(Schedule schedule, String name,
Runnable job) {
return null;
}
});
}
It will cause the actual PeriodicExecutor to not be initialized.
On Wed, Aug 24, 2011 at 6:27 PM, TG <tapestry...@hotmail.com> wrote:
> I am stuck with issue https://issues.apache.org/jira/browse/TAP5-1616. What a
> bummer, seems like AlertManager depends on threading too? :(
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/T-5-3-Alert-and-AlertManager-Tutorials-tp4732469p4732600.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
