On Thu, 19 Jul 2001 13:28:44 +0200 Jeremias Maerki <[EMAIL PROTECTED]> wrote:
> > 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. > > Well, I'm actually using SetContentHandler (in xmldb-sdk.jar) because it > does exactly what I need. SetContentHandler is a nice helper class used > in dbXML, the reference implementation and in my JDBC implementation. > Obviously that's something a lot of people can use. So why not at least > move useful helper classes (along with my JAXP stuff) into xmldb.jar? Uhh, I don't have a problem with this. :-) > > 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? > > Oh, have a look at JAXP 1.1. It's really fun to work with. Extremely > simple and powerful once you get the basic patterns. > Good tutorial here: http://java.sun.com/xml/jaxp-1.1/docs/tutorial/TOC.html Thanks for this link. > As far as I know there is only a org.xml.sax.helpers.ParserAdapter which > converts (or rather tries to convert) SAX1 to SAX2. The other direction > should be no problem to implement if you take ParserAdapter as a > template. The problem is that a Parser or ParserAdapter is not involved here. But I could imagine to write a wrapper class which transforms the catched SAX2 events to SAX1 events... -- ______________________________________________________________________ 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/ ----------------------------------------------------------------------
