- From: Laurent ROUVET <rouvet@cnam.fr>
- Date: Mon, 29 Dec 1997 10:17:08 +0100
- To: www-dom@w3.org, Alexandre Rafalovitch <arafalov@socs.uts.EDU.AU>
> Date: Fri, 17 Oct 1997 21:44:03 +1000 (EST)
> From: Alexandre Rafalovitch <arafalov@socs.uts.EDU.AU>
> To: www-dom@w3.org
> Message-ID: <Pine.SOL.3.95.971017211733.6388C-100000@charlie>
> Subject: Comments from implementing java dom classes.
>
> NoSuchNodeException extends Exception. The alternative is for it to
> extends RuntimeException. In the current case it has to be cought by
> everybody calling methods even if they know there would be no problem. (as
> Also, currently in java binding there is only default constructor and
> no constructor that takes a string. It would be nice to have one, to
> provide some feedback on why exception was thrown and not only where.
>
>
> in item(0) when items is not null. In the second case, it can propogate
> without declaration in the same way IndexOutOfBoundaries exception
> propogates for array access. (you don't want to put try and catch on every
> a[i]=j... :-}
I completely agree. I propose :
package w3c.dom;
public class NoSuchNodeException extends IndexOutOfBoundsException {
public NoSuchNodeException() {
super();
}
public NoSuchNodeException(int index) {
super("NodeList index out of range: " + index);
}
public NoSuchNodeException(String s) {
super(s);
}
}
It may be better to rename NodeListIndexOutOfBoundsException.
> In NodeList:
> prepend description refers to insertChild - should be insert.
> replace() method is declared as returning void, should be Node.
> Description for replace has following text:
> (null is returned if the index is equal to the previous number
> of nodes in the list).
> What is this _previous_ number of nodes refer to?
Could a person give an answer... Thanks.
>
> Questions on logic:
> In Node:
> getPreviousSibling, getNextSibling are traversing in breadth first
> order. Does it mean the getNextSibling on the last element _in a
> level_ would go to the first child of the first element of that
> level? That is the way I understood breadth-first traversal.
> I would have imagined that it would stop once it reaches last element
> of the level it is currently on. (level defined by a common parent).
> For example:
> x1
> |-x2.1
> | |-x3.1
> |
> |-x2.2
> |
> |-x2.3
>
> Would getNextSibling on x2.3 go to x3.1? It would for proper
Yes. I assume.
>
> getElementsByTagName is depth first. Is it prefix, postfix, infix or
> leaves only order?
It is prefix. I assume.
>
> In general, it seems that having setters for some of the attributes
> does not make sense (they are derived) and they should be read only.
> For example: setSpecified on Attribute does not make sense as it is
> an indication of whether value was supplied with setValue() or not.
> Same with setCharacter for NumericCharacterReference and several
> others.
For example:
FRAMESET cols or rows = multi-length-list [CN]
and the default value is 100%...
So, if cols attribute of FRAMESET isn't indicate you'll set specified =
false;
Regards,
Laurent ROUVET.
Received on Monday, 29 December 1997 17:28:35 UTC