Csla business logic

Before using csla, I have been using nettiers. Maybe because of my habits, I always think csla is too immature. So far, the only thing that I think is useful is its dataport data portal, the most annoying thing is his control over operations on Business Objects, which is basically useless.

His control over business objects is so limited that:

1. You cannot remove a business root object from the list.

2. You can only ....

 

Although all the difficulties can be overcome, it cannot be used as an excuse for csla's "junk" business logic.

Sub-object-parent object is the most annoying business logic setting

1. Because csla is too rigid in setting parent and child objects, we have to set the business objects to have parent and sub-object operations, so that they can be used in different scenarios (of course, you can create multiple business objects for each table, but this cannot be a "no spam" reason)

2. Business Objects use different operations. If they cannot be counted as spam in the design, the data portal can only perform root operations on the parent object (mine)

3. When using a data portal, sub-objects can only be operated by parent objects, truly becoming a child object!

4. There may be more problems

I personally think that although sometimes we can define the parent object and sub-object, just like a man in the men's restroom and a woman in the women's restroom,

However, most of the time, we still need to differentiate the business object according to our demarcation. If I want him to be a sub-object, he is a sub-object and has the operation logic of the sub-object. If he is a root object, there should be operation logic with the object. Most of the time, we don't need to be so clear at all,We only need to obtain the business objects as appropriate objects as needed. csla as a framework should implement management of business objects, including parent-child object relationships, instead of simply treating parent and child objects differently

 

Limited expression ability,ArticleChaos is the most important but least practical problem in recording csla.