This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello, right now when using LS in a WCF scenario, when the DistributedUnitOfWork has a problem trying to save changes, it throws a LightSpeedDistributedException with the following information: "Failed to commit changes to the server" And no other information anywhere about what happened. It makes debugging pretty hard as you have to try to "guess" what the UoW didn't like. Would it be possible to return more information when an exception is thrown? Regards, Vicente |
|
|
Hi Vicente, Thanks for the feedback! Currently this will be thrown if there was an issue with saving the changes and I totally agree that the error message is a bit vague, essentially though this will be caused by a validation error or error in persistance at the server. We definitely should improve this so I will post an update once we have something additional in there. The thoughts at the moment are support to allow the validation errors to be thrown at the client side and to add some debugging hooks into the service so you can recieve more details about any exceptions it may end up throwing.
Jeremy |
|
|
Hi Jeremy, This would be very helpful, as I have spend the whole day trying to find why one entity can't be saved (the same entity can be saved in a non-WCF scenario) without any luck and I am sure if I have some debugging information it would be probably a trivial thing.\ Regards, Vicente |
|
|
Hi Vicente, As a quick update on this, you can hook the GeneralFailureOccurred event within the DistributedUnitOfWorkService to get access to any exception that is being thrown. This caters for situations where you recieve back a FaultException from the service. Will keep you posted on the other changes I mentioned above.
Jeremy |
|
|
Thanks a lot Jeremy, we will start using that event to see if we can get more insight when something fails :) |
|