Gerolf Seitz 8158269b7d Remove ExercisedEvent in Event oneof. (#1067) ... * Remove ExercisedEvent in Event oneof. The Event message is only used in the Transaction message. Flat transactions do not contain exercised events, but only created and archived events. Therefore we can remove the ExercisedEvent from the Event oneof, without breaking transport compatibility. HOWEVER: The Java Bindings used to use the data.Event class for both flat transactions and transaction trees. To properly represent the actual event types in the two transaction structures, 1) Event is now and interface and is only used in the Transaction class. 2) there is a new interface TreeEvent, which is used in the TransactionTree class. * CreatedEvent implements Event and TreeEvent * ExercisedEvent implements TreeEvent * ArchivedEvent implements Event Some "pathological" cases where an occurrence of an exercised event would have resulted only in an exception, are now removed (see change in LedgerApiV1.scala). Fixes #960.		2019-05-13 14:36:13 +02:00
..
bindings	Remove ExercisedEvent in Event oneof. (#1067)	2019-05-13 14:36:13 +02:00
bindings-rxjava	Remove ExercisedEvent in Event oneof. (#1067)	2019-05-13 14:36:13 +02:00
codegen	Daml lf type safty (ChoiceName, VarName, FieldName, ConstructorName) (#983)	2019-05-13 11:17:12 +00:00
testkit	Remove ExercisedEvent in Event oneof. (#1067)	2019-05-13 14:36:13 +02:00
BUILD.bazel	Enforce consistent formatting of BUILD files. (#412)	2019-04-12 13:10:16 +02:00