Rolled our own Tx Management (pretty simple transaction queue). As for the XML thing. the problem can be solved by handling the serialization manually and overriding the serial ID's etc... to pick up when an "old form" of the object is being read in.
The xml thing would have given us a fill in those fields that are available and set others to defaults approach. The DTD would maybe change slightly but you could handle backwards compatibility for free. Our solution, "don't ever update the model" or when you do reinstall. The app has no long term reporting requirements and the product catalog is constantly changing. Translation, update = delete old & install new. Happy to share the code. In addition, to the new Java XML serialization we tried betwixt & digester from the apache group as an approach. Neither got all the attention and love they needed, so I still think it is possible. -Todd __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
