Issue: bpel editor validates a throw activity in a nested scope of a termination handler as an error.

Reproduce: 
Import the attached bpel project into netbeans and open the bpel file "pTH15Process.bpel" and notice the validation
error reported for the throw activity "Throws_NewFault" which is in the scope "ScopeInTH" of the termination handler of
the scope "OuterScope".

What the spec says: 
section 12.6 states

"However, a termination handler cannot throw any fault. Even if an uncaught fault occurs during its behavior, it is not
rethrown to the next enclosing scope. This is because: (a) the enclosing scope has already either faulted or is in the
process of being terminated, which is what is causing the forced termination of the nested scope".

This is interpreted as there should be a throw activity that is a direct child of the termination handler, but a throw
activity inside a scope that is a child of the termination handler is permitted. The explicit or implicit fault handling
of that scope will handle the fault thrown, but the fault will not propagate outside the boundary of the termination
handler. 

Solution: With this the editor should only validate as an error, a throw activity that is a direct child of the
termination handler and not a throw activity that is in a nested scope of the termination handler.