Stax bug: writeEmptyElement not closed

Question

Hi,
The following test case:
xsw.writeStartDocument();
xsw.writeEmptyElement("test");
xsw.writeEndDocument();
xsw.flush();
xsw.close();
Produces:
<?xml version='1.0' encoding='utf-8'?><test
And the tag is not closed.
Looks like the logic doesn't cope with one empty element in the document.
An egde case it has to be said but one we need...
Thanks,
M

Answer 1

ups, forgot: using kodo 2.5.8
Stefan wrote:
Hello again ...
My code looks now like the following:
q = pm.newQuery(SchuldnerKonto.class, "kontoNr=="1234"");
for (Iterator it=result.iterator();it.hasNext();) {
it.next();
As far as I read the documentation and newsgroups, I would expect, that
the code above closes the resultset by itself, so that I don't have to
call
q.closeAll()
It works fine, as long as the resultset (LazyResultSet) contains at least
1 row.
When the resultset is empty, the query stays open, so that I get more and
more open session (using Oracle 9i)
I often use wrapper classes/methods around queries, which only return the
Collection that the query returned.
When using these wrapper classes it is of course mandatory to iterate the
Collection to the end.
Due to the bug(?) above that whole logic isn't working, at some point
oracle refuses to give new connections and the application hangs.
What can I do about it ?