Hi all, So we now have 2 proposals for our easier BPEL language specification in the wiki. Both of them are partial although the intersection covers most of what needs to be covered I believe:
http://cwiki.apache.org/confluence/display/ODExSITE/BPEL+Simplified+Syntax+%28simBPEL%29 Don't see any conflicting views in the fact that there are 2 proposals, it's just that those stuff are better thought out f2f and it was fairly easy for myself, assaf and alex to work on it on one side and Tammo and Oliver on the other side. Actually the two proposals are surprisingly similar, especially in their Javascript influences and complement each other nicely. Great minds think alike. So now what we should do I think is try to reconcile these 2 proposals so we can start formalizing a grammar (I actually already have a partial one that will be fairly easy to tweak to adjust to our choices). The main difference I see is that in the second proposal (assaf/alex/myself, I'll call it AAM now on) we've tried to let go of WSDL for environments where it wasn't necessary. Basically when you're using a Java process engine directly embedded in your program, you don't really need WSDL, just a callback interface (and then endpoints, being opaque to the engine, can be implicit). So there's no declaration of services in AAM and we stick with partner links (that would then be associated with a service in a deployment descriptor only when needed). On the other end the first proposal (tammo/oliver, I'll call it TO now on) is more explicit with service specifications in the process and also with variable declarations. Beside this, several things are almost identical. The syntax for invoke / receive is similar, scope definitions have a lot in common (although AAM separates error handling and event handling), flow and sequences are identical (just par vs. flow and seq vs. sequence) Also in AAM there's nothing about scope links as TO had specified it before we started thinking of it and we actually liked it (it's actually the biggest part of TO). Similarly there are a few stuff in AAM that aren't in TO but that would make sense there as well. So any opinion on both proposals? What are the parts that you like better? Tammo, did you have a look at AAM? Thanks! Matthieu
