Finding Observability Failures

Dec 2, 2009 at 3:21 AM

Is there an easy way to determine which methods don't have mappings registered yet?

When we built our framework, we decided to throw exceptions when method mappings weren't found.   We had exceptions when the target object and arguments were immutable, and that made it rare to see the exceptions come up in practice.  This allowed us to find out right away if an expression was going to work without testing each expression by itself.

It would be nice of there was a way to get some sort of debug output on failed observability when ExpressionObserver is used to build an observer tree.

Dec 2, 2009 at 8:15 PM

I guess it may be a good idea to build some tracers in the ExpressionRewriter. An external tool could analyse the results and detect problematic methods. I might also be possible to build a mapping from the generated transformation pipelines to the original expression tree. That would help a lot when debuging lambda expressions made observable.

Aug 26, 2010 at 5:39 PM

Thomas - any updates on this?  Debugging traceability would really help us to know exactly why things are firing.

Please let us know.  Thank you very much!