Vibrant discussion about CSLA .NET and using the framework to build great business applications.
I have many objects with several complex async business rules and I'm finding if there is an issue it's a bit maddening to try to figure out why IsBusy is stuck on a business object.
Specifically if I call checkrules when loading from the db and isbusy get's "stuck" I have to comment out each rule one by one until I find the one that is sticking. This is not optimal.
I can't find any documented way to tell *why* the object is busy and I'm imagining a future scenario where my product is released and a user reports a tech support issue where a screen is just showing a busy icon and they don't know why and I can't tell them why because I have no way to automatically report what's going on specifically.
There is a way to check if a specific property is busy but many of my properties are associated with more than one rule and this isn't helping to automate reporting what is busy.
Is there some way to tell why an object is busy?
Yes,
Asyncronous rules can be a PITA.
No, there is no provision for a list of property and the rule that is causing the property to be busy. The rule engine only maintains a list of BusyProperties - but not which rule that caused the property to become busy.
Added to the wish list.
http://www.lhotka.net/cslabugs/edit_bug.aspx?id=1034
Jonny Bekkum, Norway CslaContrib Coordinator
Thanks Jonny!