[EMAIL PROTECTED]">We use inheritance of the java classes and create separate deployments for each customer application.So, I invite your thoughts:
- How are others out there managing to support multiple clients, whose structural data needs may vary somewhat, while maintaining the integrity of the common code all clients depend on?
[EMAIL PROTECTED]">Based on our experience I'd say it was the only solution. Otherwise you have a maintenance nightmare with any but the most trivial classes. We have a fairly complex graph of EJBs for representing an Organization with multiple addresses, contacts, phones, notes, etc.... We have encountered numerous bugs in the past three years. It would have been a nightmare to manage completely different sources for each different deployment.
- Is inheritance a good route to pursue to solve the problem?
[EMAIL PROTECTED]">Only if you are stuck with your current IDE. You might want to consider XDoclet or Together. But I don't rely on automatic code generation. Since we expose only the most important date and relationships in the entity interface, our interfaces are fairly stable. Adding a method every now and then is no big deal.
- Should I resign myself to having one giant "all-inclusive" schema for all clients with possibly many sparsely populated columns because they are used only by certain clients?
--Victor
[EMAIL PROTECTED]">
