jaikiran pai wrote:
Just wondering whether this is OK. The only side-effect that I can think of, with this implicit rule for asynchronous method, is the difference in transaction semantics for that method invocation.
It's likely not OK.
Also not OK is the fact that I'm checking the actual java.lang.reflect.Method (and ignoring the class-level) instead of going to metadata. At the moment the interceptor is client-side and we've no access to the metadata. All this has to change, but for now I've got hacks like this (noted with TODOs) just to get some baseline that the mechanism is generally working.