Hi.
I think you have to apply XP (extreme programming) there. Usually database does not change every day.
If this is a case, something wrong is going on. Maybe there is no global planning.
When something in the database change, usually you don't need it now, so, you can leave it afterwards.
Is easier to keep up to date the generated code than typing.
Also, there is a book called 'Pragmatic Programming' that talk about it.
I hope it help you.
Gus.
-----Mensaje original-----
De: Ken Burcham [mailto:[EMAIL PROTECTED]]
Enviado el: Monday, January 06, 2003 08:02
Para: [EMAIL PROTECTED]
Asunto: Re: [castor-dev] how high is the cost of maintenence of castor xml in real world?
Kai,
I've worked with generated source in production projects (even if not so much with castor) and I would think there are two possible responses:
1) Use the source generator as a way to get started. Then maintain the schema/dtd+castormapping+javaobjects by hand thereafter, no longer utilizing the source generator.
2) Do not put any functionality aside from what the source generator generates in the castor objects. Use them only for persistence so that any bug fixes would be structural changes that would require updating the schema/dtd and then source regeneration.
Either way, you just don't want to be in a position where you ever regenerate your source and then have to touch anything by hand. That's when it starts getting expensive. Personally, since #2 never seems to work right, #1 is where I usually land.
Hth,
ken.
