[jdom-interest] Strange Element.addContent(index,Content) problem
Bradley S. Huffman
hip at cs.okstate.edu
Mon Mar 22 06:46:16 PST 2004
Hmmm, print out elmt's children and see what's there. What version of jdom?
Brad
Kai Woerner writes:
>
>
> Bradley S. Huffman wrote:
>
> > Use getContent instead of getChildren. getChildren gives a list of *only*
> > the element children.
>
> But the element elmt does only contain element children - no mixed
> content whatsoever.
>
> Kai Wörner
>
>
> >
> > Brad
> >
> > Kai Woerner writes:
> >
> >
> >>I'm experiencing a very odd problem with
> >>Element.addContent(index,Content). This is an altered snipplet from the
> >>code I have:
> >>
> >>elmt.addContent(440, newComm);
> >>System.out.println("@inserted at:"+elmt.getChildren().indexOf(newComm));
> >>
> >>(elmt being a legal element in a jdom-tree, newComm being a new Element)
> >>
> >>- this would output "inserted at: 220".
> >>
> >>Of course the code is a bit longer and more complicated, but these two
> >>lines are exactly like in my code and the result is alwayy the same:
> >>elmt.addContent(200, newComm) would result in 100.
> >>
> >>Anybody having experienced something like that?
> >>
> >>Thanks,
> >>
> >>Kai Wörner
> >>
> >>_______________________________________________
> >>To control your jdom-interest membership:
> >>http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourho
> st
> >>.com
> >
> >
More information about the jdom-interest
mailing list