Just a quick warning, there's a couple of minor API changes coming soon in
the next release, I hope they don't cause too many problems for anyone.

The first one is in ElementHandler. Its becoming the following interface
instead.

public interface ElementHandler {
    public void onStart( ElementPath path );
    public void onEnd( ElementPath path );
}

For those making their own Element implementations the following other
change that may affect you.
I've made a performance patch in DocumentFactory from this

    public Element createElement(QName qname, Attributes attributes) {
        return createElement( qname );
    }

to this.

    public Element createElement(QName qname, Attributes attributes) {
        return new DefaultElement(qname, attributes);
    }


And there's now a constructor in DefaultElement like this...

    import org.xml.sax.Attributes;
    ...
    public DefaultElement(QName qname, Attributes attributes)
        ...
    }


So next time you come to upgrade to a newer dom4j version or daily build
could you make sure you also override the createElement(QName, Attributes)
method to return your derived Element type and that you add a
MyElement(QName, Attributes) constructor too? Otherwise you won't get your
derived Element types returned when using using SAXReader.


Sorry about those changes - things should be pretty stable from now on.
(We're getting close to 1.0).

James



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
dom4j-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dom4j-dev

Reply via email to