[jdom-interest] getMixedContent -> getContent
jhunter at collab.net
Wed Jun 27 13:04:23 PDT 2001
> Yes, it's always been so. IMHO, we should do an s/Children/Elements/
> on the API.
No one took the bait so you're starting the debate on your own, eh? :-)
Here's a little test to help answer the question:
<!-- The sky is blue -->
How many children does root have?
The current getChildren() naming model says it has one child.
> (b) you accept the consequences and have to explain very clearly what
> "children" means every time someone asks,
Easy consequences to accept since no one's ever asked. :-)
I could live with getElement() / getElements(). It just seems less
appealing because then you're having to imply it's the first-level child
elements that you're getting. The getChildElement() naming is more
explicit but feels like explicitness overkill. That's why we haven't
changed things. I think we're generally lukewarm on all options -- and
since no Joe Users have complained we haven't worried about it.
More information about the jdom-interest