Temporal rules does not work after restart

[manucarrace]

In the event of a restart, the temporal rules stop working.

It is also known that temporal rules need a context started (or active) to work, that means that a initial foo notification must be sent.

Both problems are related. We should avoid initial notification or send automatically these initial notifications in case of restart or new time-rule provision.

[manucarrace]

Example of temporal rule:

{
	"name":"Timer_example",
	"text":"select *, current_timestamp.toDate() as currentTS from pattern [every timer:interval(10 sec)]",
	"action": {
		"type":"update",
		"parameters":{
			"id":"timer_example_min_2",
			"type": "ww",
			"attributes": [
				{
					"name":"timestamp",
					"type": "Text",
					"value": "${currentTS}"
				}
			]
		}
	}
}

[fgalan]

@cblanco @aarranz you did some modifications in Perseo Core related with time rules in the past (PR telefonicaid/perseo-core#114). What do you think about this? Any idea?

[manucarrace]

Using the ESPER simulator:

If we include the time-rule in a partitioned context it does not work:

If then, we stimulate with an event, then it works:

Creating a specific context for time-rules seems to work without any further context activation. This could be the solution:

[fgalan]

Fixed in PR #415