> Would you say it's worth working on the protected and private
> javadoc as well? When I work on code that I'm
> developing/maintaining, as opposed to using a public API, I usually
> run javadoc with the -private option for my own reference.

If you wish, you can do this. Though I do not think that we should deliver
javadoc for private and package-local methods, because those are only for
JayBird developers. And some private methods are more-or-less
selfexplanatory, so we can save efforts there.

> I'm not sure if you're referring to the XdrOutputStream fix, bug if
> you are, I should warn you that I posted a new bug and fix today on
> the sf.net bugtracker ([ 1050584 ] Invalid parameters / server
> lockup), and you may want to take a look at that as well before
> 1.5.4 gets released.

No, I was talking about the new bug report, I have seen it and will check it
on the weekend.

Roman