This is a rather general question.
I can see how java xml binding can save me time up front. I am wondering
about the maintenence cost.
People generate a set of classess from either schema or dtd to do marshall
and unmarshall. Should the generated source files be put in source
control?
If there's a bug in the generated file, it should be fixed in source
control.
But later if castor is updated, and should the updated castor be used to
generate source files? The bug fixes already made into an organization's
source control need to be checked to see if the latest version of castor
fixes those bugs already?
If later, the dtd or schema is updated(some elements are changed, new
elements are added), castor needs to be run to generate source files from
the updated dtd or schema. Then the content of newly-generated files can be
different from the existing files. Then the bug fixes to the existing
files need to be check to see if it's needed for the new files.
I am wondering if this is how it's done in real world.
I am concerned that the cost I can save up front can be much less than the
maintenence cost. Can I be better off writing my own classes to handle
the java xml binding?(no, I don't mean writing a code generator. I mean
using a parser to read XML and make some objects out of it, just like the
generated classes).
I really need a quick response......
Thanks.
Kai
_________________________________________________________________
�������������ĵ����ʼ�ϵͳ�� MSN Hotmail�� http://www.hotmail.com
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
