CSLA supports an easy way to develop business objects. But how do I implement use cases? That is, where do I put the code that goes beyond the responsibility of individual business objects? We use Task classes to accomplish that. But does CSLA prescribe a ready-for-use solution for this common problem?
Thank you very much in advance for your answer!
We often call this a UnitOfWork (UOW) model and it translates into a
For non-CRUD operations on a database we use CommandObject (from CommandBase).
i understand the idea of task objects, or as johnny adviced, uow, but how do you "glue" them together?
point 5 of rocky's post http://www.lhotka.net/Article.aspx?id=40048e03-6f9e-44a4-8322-80cb5de8303a describes the process object consisting from command objects, but this does not seem to be a "standard" pattern.
Also found a post on orchestration pattern idea http://codereview.stackexchange.com/questions/25435/sequential-execution-orchestrator-pattern. Looks quite clever as well.
I dont exactly know how to approach this. Curious on your ideas!
Copyright (c) Marimer LLC