Hello everybody,
I have the following issue with the CSLA framework that I hope you may be able to help me with.
Currently, I have two root objects: Activity and Employee. Since this is a sort of planning application, I want to be able to assign an Employee to an activity. The application will be responsible for checking that an Employee is available to perform the activity.
The Activity object has an AssignedEmployee property. When I assign an Employee to the AssignedEmployee property, I check the availability of the Employee using a custom validation method. This is were the "trouble" starts.
1) A significant amount of time may pass between the Activity.AssignedEmployee = SelectedEmployee call and the Activity.Save() call. In this time someone else may have assigned and saved the Employee to another Activity as well. If this would be the case, the former Activity object would have become invalid as the Employee is in fact no longer available for the job. How can I make sure the Activity object is revalidated when Save() is called, even if it did pass validation at assignment? I would prefer this validation to be performed in the context of a transaction. Can I just call ValidationRules.CheckRules inside DataPortal_Update?
2) For the validation rule, I took the approach of the book, and used a IHoldEmployee interface and a static ValidAvailableEmployee method which checks the availability in the underlying database. Because a second connection is opened to the database, the hated DTC error appears. Can I use the LocalContext object to work around this?
Thank you very much in advance,
Jos
JdZ:
1) A significant amount of time may pass between the Activity.AssignedEmployee = SelectedEmployee call and the Activity.Save() call. In this time someone else may have assigned and saved the Employee to another Activity as well. If this would be the case, the former Activity object would have become invalid as the Employee is in fact no longer available for the job. How can I make sure the Activity object is revalidated when Save() is called, even if it did pass validation at assignment? I would prefer this validation to be performed in the context of a transaction. Can I just call ValidationRules.CheckRules inside DataPortal_Update?
2) For the validation rule, I took the approach of the book, and used a IHoldEmployee interface and a static ValidAvailableEmployee method which checks the availability in the underlying database. Because a second connection is opened to the database, the hated DTC error appears. Can I use the LocalContext object to work around this?
Yes, that's why the LocalContext was created. Put the connection there, and have your object check if there's an existing connection to use already. But I think if you do the check last, you won't need to call this rule again, thus avoiding this problem.
Copyright (c) Marimer LLC