I have tested it for myself. It worked fine. I even posted an example showing you that it worked. All we're asking is that you post the code that you want us to test, and we'll be more than happy to test it. Posting an entire program that contains other logic doesn't really help us, so we've asked several times for an SSCCE. Without that, we have to chalk this up to an error on your part. That's not a personal offense, but hopefully it is a lesson learned: when you see something weird, chances are you're doing something wrong.
Yes but not of the other error, the writing bytes one, the one HelloWorld mentioned. Obviously there's an error with java with THAT one.
You people seem to be obsessed with proving me wrong. In fact, you pointed out the error yourself. The write bytes was only writing 1 line of the code - it shouldn't have been. Since I wasn't including the 3rd field, it should've just been creating a new one.
I've heard 20 "you're wrongs" so far - even before people have read my argument. Interesting.
You seem obsessed with proving everyone else wrong, when you've clearly provided no counter-arguments to the factual information given to you by everyone else. The API states a behaviour, you experienced that behaviour, it is not an error. Please get more practice in reading the Java API, as you're obviously struggling at the moment.
It's pretty clear that what happened was you made a programming error or didn't understand the API you were using. That's okay, but it's not a bug in Java. Like I said back in my first reply, resorting to blaming the language or a compiler or a tool instead of yourself is a pretty common novice mistake, and *that* is what we're trying to help you understand.
But if all you want to do is bicker, I can lock this thread. I'd much rather you post the code you're talking about so we can help you understand what's going on, but it's up to you.