Fixed. I've chosen the robust solution, so a <for>@BPEL2F as well as @BPEL2D is allowed in a <wait>@BPEL2F.
Fixed for wait, onAlarm, forEach and the event handler getter in Scopes.
I would probably have voted for a warning in the compiler, since in schema validation terms the @BPEL2D namespace is technically an extension namespace in an @BPEL2F process document.
Yeah, makes sense. I changed it again - now such children are expected to be in the same namespace as the parent element. Others are treated as extension elements.