Claudio Guidi

In Jolie there is the primitive instanceof for testing the match of a variable against a type. it would be nice to extend such a primitive instead of introducing a...

I think we need both the possibilities. At the beginning deep copy was used rarely, but now is widely used because of the new syntax of inline trees. Intuitively,

Mmmmm ` ` the inner elements of messages are joint only with sum schema types. This is why the message is built with sum and not with prod. I think...

This is a possible solution but in this case you will loose the mapping between the type names in jolie and in the wsdl. Maybe, jolie2wsdl could resolve the ambiguities...

In general it is always a good practice also in jolie to use different type names for each message.

which is the difference with: scope( s ) { /*\* code **/ releaseResource@ResourceManager()() } ?

ok. Something like this? scope( a ) { install( default => releaseResource@ResourceManager()()); scope( s ) { install( myFault => ....; rethrow ) /\* rethrow is missing now _/ /_\* code...

ok. so what about this? scope( a ) { /*\* code **/ } ; releaseResource@ResourceManager()()

Ok, but this is a case of bad programming

I am trying to see the evidence of the benefit to introducing a new kind of handler. We already have default, this and fault handlers. I am not so sure...