> com.customerdomainname.entity.web.project.eshop.shoppingcart.SCManager
> find & replace all "customerdomainname" to "cdn". I'm going to assume customerdomainname actually varies here. Sometimes, people really go overkill with this type of organization. You really don't need to make that many levels. I mean, you're convoluting it by making it so deep, and you're not taking advantage of what OOP can really do. There have to be common methods to all the shopping carts, right? Make a shopping cart class that is independent of whoever the customer is, and if you need custom methods for specific customers, just extend the methods of the generic shopping cart class. shoppingcart customerdomain.shoppingcart extends shoppingcart I find no compelling reason to organize my classes to such extents. I'd rather not have to dig down through 6 folders to find a class if I don't have to. Yes, a certain amount of organization is good. inc/ui inc/shoppingcart inc/data etc. _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
