Fabrizio Montesi

Dear all, I've opened the GitHub discussions feature to have open-ended discussions like these. Let's try it out to see if we like it. :) For this issue, please continue...

Cool (ironically). Any ideas on what might cause this?

Ah, but then we could change jolie2wsdl such that it generates separate wsdl:message nodes for each operation, rather than for each type.

If you look at this: ``` ``` the problem is that both sum and prod have the same input and output message declaration, OpRequest and OpResponse respectively. We should not...

It seems that WS-I basic profile disallows reusing the same message for different operations. It works only if one adds ws addressing on top. I suggest to keep it simple...

I think it's a bug, in the sense that we should exit with an error for now. It becomes an enhancement if we open a new issue where we want...

I'm not fully convinced that this should be in the language. Isn't this usually just dealt with by the debugging tool? For example, by telling it that you want a...

I would just edit all process implementations, e.g., `SequentialProcess`, such that they ask the interpreter permission to proceed (and possibly wait because of it) before taking the next step or...

Multi-threading: That's a challenge, we should probably get some inspiration from the debugger in netbeans. But basically, we'll have to deal with the fact that multiple processes would be running...

That if you have a fault in your code then that release won't be executed, differently from the finally block in Java, which is always executed even if you have...