I think not - these ideas are different.
The idea of AOP is to develop cleaner code, better encapsulate it, simplify and simplify systems. This is an idea focused mainly on developers.
WWF's idea is to build enterprise applications from pre-built blocks. Intentionally somewhere between developers and business intelligence. With WWF, you can reuse some modules in new contexts, but as a rule, WWF tries to resemble the concepts of business process modeling .
Of course, you can imagine many situations where you can use WWF as a tool to achieve better encapsulation and weaken the connection, or otherwise use AOP to reuse modules and organize it in your workflow. But the intersection of their common ideas is quite small.
source share