>From the DTD it looks like a JDO config (commonly named database.xml) can have refer to only one database, however I do not see anything to stop you having many jdo objects, each having a different configuration file (i.e. database1.xml, database2.xml, ..., databaseN.xml)
Anyone disagree? Conor -----Original Message----- From: Mark Cornelius [mailto:[EMAIL PROTECTED]] Sent: 09 January 2003 12:20 To: [EMAIL PROTECTED] Subject: [castor-dev] multiple database.xml? How does castor handle multiple databases, e.g. multiple jndi sources for a single application? Can I have more than one database.xml? or can I specifiy multiple databases in a single database.xml? ____________________________ Mark E. Cornelius Phi Beta Sigma/Prince Hall Mason The Woodlands, Texas I had fainted, unless I had believed to see the goodness of the LORD in the land of the living. Wait on the LORD: be of good courage, and he shall strengthen thine heart: wait, I say, on the LORD. " Psalms 27:13-14 ----- Original Message ----- From: "Keith Visco" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 08, 2003 10:23 PM Subject: Re: [castor-dev] XML Schema code generation and bound properties > > Hi David, > > Sounds like a bug to me, I'll try to get that patched up in the CVS > ASAP. You may wish to file a bug via our buzilla for tracking purposes > (http://bugzilla.exolab.org) > > Thanks, > > --Keith > > David Green wrote: > > > > Using the source generator from XML Schema, I've noticed that some bound properties (notably the ones with the _has_foo) are generated as follows: > > > > public void setContent(boolean content) > > { > > java.lang.Object oldContent = new Boolean(this._content); > > this._content = content; > > notifyPropertyChangeListeners("_content", oldContent, new Boolean(this._content)); > > this._has_content = true; > > } //-- void setContent(boolean) > > > > The property change listeners are fired before the _has_content is set, thus causing problems when attempting to marshal the class from a property change listener. Shouldn't the set method look like this: > > > > public void setContent(boolean content) > > { > > java.lang.Object oldContent = new Boolean(this._content); > > this._content = content; > > this._has_content = true; > > notifyPropertyChangeListeners("_content", oldContent, new Boolean(this._content)); > > } //-- void setContent(boolean) > > > > If there's a good reason for the existing code generation, please let me know. Otherwise, can someone commit a fix for this? > > > > Thanks, > > > > David > > > > ----------------------------------------------------------- > > If you wish to unsubscribe from this mailing, send mail to > > [EMAIL PROTECTED] with a subject of: > > unsubscribe castor-dev > > ----------------------------------------------------------- > If you wish to unsubscribe from this mailing, send mail to > [EMAIL PROTECTED] with a subject of: > unsubscribe castor-dev > > ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev -- This e-mail is confidential and is intended for the named recipient only. If you receive it in error please destroy the message and all copies. Kainos Software Ltd. does not accept liability for damage sustained as a result of malicious software (e.g. viruses). Kainos does not accept liability for, or permit, the creation of contracts on its behalf by e-mail, the publication of any defamatory statement by its employees by e-mail, or changes subsequently made to the original message. The Company's registered office is located at 4-6 Upper Crescent, Belfast, BT7 1NT, Northern Ireland, Tel +44 28 9057 1100. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
