Re: archives?
Gary Shea wrote: Just joined today, trying to find out more about the discussion wrt chained exceptions and XMLDBException. Can't find archives for this list for any year other than 2001. Are they out there somewhere? The (now) chained exceptions XMLDBException is fairly trivial. What you have to do is: 1) cvs co the xmldb module (see xmldb.org) 2) build it 3) import the libraries into your project 4) query/replace the calls of 'new XMLDBException' That's all folks! -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
Re: FW: Configuring an XML:DB database
Hi all, any news on this? -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
Problem with xupdate and xerces-1.4.3
Hi all, one of our users has a problem with XUpdate and it seems that it's because XUpdate needs xerces-1.4.3.jar and Xindice needs xerces-2.+.jar. Sure enough there will be problems if both jars are in the classpath at the same time. Anyway, it there any plan to upgrade xupdate to use the latest version of Xerces (BTW they have a brand new version out there)? -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
Re: Addition to XAPI: getNames()
Whilst I agree that getName() is a special case of getNames(), isn't it perhaps a bit harsh to remove getName() - this would break all of the applications which are directly using the getName() method. (Even if all driver vendors update their implementations immediately.) Perhaps it is better to leave it in, but making it clear that the method will be removed later? simply use the deprecated flag for the getName() method. I thought about : Iterator getNames() and maybe String[] getNames() would be better since it's much easier to initialize statically -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
Re: FW: Configuring an XML:DB database
What about the Configurable interface? Database extends this
interface. What do you mean by a very good support?
More about the subject:
If you have a Configurable interface, you still need to trigger the
initialization (after all configurations are done).
One possibility is to do it in the getCollection method:
public Collection getCollection() {
if (!initialized) {
... initialize the system ...
initialized = true;
}
}
The problem with this approach is the potential delay between the
configuration and the actual intialization and the feedback you may receive.
If you set up your system and for example the database's location is
unreacheable, when would you like to receive the notification? when you
start your server or when a user call the getCollection method,
potentially hours after you started the server?
Both alternatives are justifiable and I think that the API should
provide a way to implement them both (i.e. introduce an 'init' method to
initialize the system).
-Vladimir
--
Vladimir R. Bossicard
www.bossicard.com
--
Post a message: mailto:[EMAIL PROTECTED]
Unsubscribe:mailto:[EMAIL PROTECTED]
Contact administrator: mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
--
Re: XMLBDExceptions and chained exceptions
If this would help to make development of vendor implementations like Xindice and application development easier I'm +1. What about backward compatibility? Method will only be added (and not removed or their signature modified) so it shouldn't be a problem. -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
XMLBDExceptions and chained exceptions
Hi all, From the Xindice POV, it would be very helpful to have the 'chained exceptions' implemented in the XMLDBException. Just like in the JDK 1.4. I'm volunteering to do it if you decide to go in that direction. Regards, -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
Re: FW: Configuring an XML:DB database
What about the Configurable interface? Database extends this interface. What do you mean by a very good support? but after setting several properties (like database location), you usually still need an 'init()' method. Maybe an 'Initializable' interface could solve the problem? -Vladimir -- Vladimir R. Bossicard www.bossicard.com -- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe:mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ --
