logo       

[xmlc] 2.3beta getElementById() behavior: msg#00014

java.enhydra.xmlc

Subject: [xmlc] 2.3beta getElementById() behavior

I said I'd report any bugs that I saw in 2.3beta, so here it goes. :-)

Didn't I read that one of the changes in XMLC 2.3 was that the element-by-id
mapping was cached and getElementById() was just using the cache and not
traversing the document?

This is causing a problem for me. In my code, I'm setting the id of an element
in one place and then attempting to look it up by its new id elsewhere. This
was working back in 2.2.

Will it be possible to update the cache when element.setId() is called? If
not, can I disable this caching?

Cheers,
Erik


--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise