in a recent project, i have a scenario set up like this:

• Namespace Business_Objects:
• BaseBOs
• CustomersBO
• ContractsBO
• ContactsBO
• ClientsBO..
• Customer Maintanance
• CustomersBO (subclasssed from BaseBOs CustomersBO)
• ClientsBO (subclassed from BaseBOs ClientsBO)
• ..
• Contracts Maintanance
• CustomersBO (subclassed from BaseBOs CustomersBO)
• ContractsBO (subclassed from BaseBOs ContractsBo)
• ..
• .. and so on

i was wondering if anyone got some naming convention advice for the subclassed bo's to reduce confusion.

Something like CustMaintCustomersBO and CustMaintClientsBO ... ContrMaintCustomersBO..
but then i have a namespace like customerpropertiesgroups and one customerproperties. So i cannot name them like custprop..something because it could be confused with either one.

not sure. i have around 15 BO's in total, and not all of them are subclassed in each namespace, but still its quite alot of bo's going around.

How do you name your bo's in such cases ?

Thanks

At this point, I don't think you do. There is a feature request in to allow the marking of a BO as one that won't be built, but that hasn't happened yet. This would be used in cases like this and also for base BOs, which also aren't built (or configured in the BO Mapper).