On Wed, 18 Jul 2001 14:41:48 +0200 Jeremias Maerki <[EMAIL PROTECTED]> wrote:
> Hi there > > I just noticed the nice SetContentHandler class in the SDK. When I took > one more look around the SDK I noticed the Simple* classes which in my > oppinion don't make much sense. I don't use/need them in my > JDBC-implementation. Anyway. I'd like to propose a merge of xmldb.jar > and xmldb-sdk.jar. That won't hurt the xmldb.jar much and if the drivers > need classes from the SDK, the target application need to include 3 jars > only for XML:DB. Windows still suffers from classpath-length problems! This might be true. But you need the 3 jars only if you want to use the reference implementation. In your case (JDBC) you simply add xmldb.jar to your CLASSPATH. If others also complain about this separation we can reconsider the situation. > To compensate for my comment above I have attached two helper classes > that might be a useful addition to the Java-XML:DB-API. They can be used > in the context of JAXP 1.1 transformations and XML:DB. Please look at > the javadoc usage example in XMLResourceInputSource. Even if I didn't use JAXP 1.1 so far (only 1.0) - and with this I don't know the transformer package - I think these helper classes can be a useful extension. Other ideas? Btw: Is there any possibility to transform SAX1 <-> SAX2? Some packages only accept SAX1, but the XML:DB API provides a ContentHandler (SAX2). Lars -- ______________________________________________________________________ Lars Martin mailto:[EMAIL PROTECTED] SMB GmbH http://www.smb-tec.com ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
