June 2007:
1. Unification is not good. A violation of a message out of the scenraio order might be ignored:
	Note for this bug and fix:
	1. The problem is relevant only for messages. Other construct are immidiate.
	2. The problem arises only when one or more from sender/reveicer are null. Since later
	   they would no be null any longer, so unification will fall but there should be violation.
	3. So when one or more is null: at the end of the case we add a condition that always states the same:
	   if both sender and target are equal then unification = true.


July 2007:

1. Partial order bug: In getCutState there are several mathods reffering to the same one - causes
the EE hashmap to be empty (getting empty during the strategy execution). There is no violation 
but if it is execution then nothing happens. Fixed 8/7/07

2. Another partail order bug: Lifeline and variable binding in case of partail order might
get messed. (varaibleBindingState and lifelineBindingState) Fixed: 11/07/07

3. And another partail order bug: Combined fragment with partial order - Not working.
   The last cut feature in the compiler is wrong. Need to be fixed.  -FIXED	
   
4. Immidiate events afetr a CombinedFragment will cause errors  - FIXED

5. Two messages with the same name in the same chart do not allow different varaibles names - minor, will be fixed
	on more demand. 
	
6. 31/07: coordinator problem. Recursion in coordinator was solved using mutex. Proved to be wrong solution, 
dependes on the parity of waiting event. New solution: return to the old coordinator architacture but if
there is no cut cahgen in none of the LSC do not call the strategy and don't execute anything... Also wrong
Sometimes there is a change in LSC x but not LSC y and the enabled event might be execture again and
again in loop for ever. Final solution: Use mutex + queue. When coordinator execute method it is locked
it can not execute more than one method in a given time. requeset for getCutstate are going into queue
and will be execture one after the other later.