[Bluestone] Persistance Issues with Bluestone

I've been working with a client that is running the HP Bluestone software as their app server, and I have discovered some faily major persistance issues with it. I was wondering if anybody else has had experiences like this with Bluestone and what they did to correct the problem.
We are using CMPs against an Oracle database, and had an issue where if a field in one record was populated, but the same field in any other record in the transaction was null, all records in the transaction would get the value of the one record. This issue took about four months of working with Bluestone to correct. (And in the end, they said, "Oh, this is a known issue--here's the patch." And then the patch didn't work when we tried it and we had to get another patch.)
Now, I have an issue that is excatly the opposite. The field is NULL in the database, but when the record gets read into the bean , the NULL value is not translated to the bean. Instead, the bean retains whatever information was there from the last use of that bean. I have contacted Bluestone again, but basedon the last response time, I'm not overly hopeful of a quick resolution.
Has anybody had these issues before? Is there an easy fix? I'm thinking of switching the beans over to BMP so that I can control the persistance and not rely on Bluestone's apparently shaky CMP, but before I do that I was wondering if there was anything simple to do.

Joel,
I am the engineer that works closely with your client and I support the HP Bluestone software products. We have been recently contacted by your client, and they report that this issue you have is in fact completely end-user code related.

Originally posted by Joel McNary:
I've been working with a client that is running the HP Bluestone software as their app server, and I have discovered some faily major persistance issues with it. I was wondering if anybody else has had experiences like this with Bluestone and what they did to correct the problem.
We are using CMPs against an Oracle database, and had an issue where if a field in one record was populated, but the same field in any other record in the transaction was null, all records in the transaction would get the value of the one record. This issue took about four months of working with Bluestone to correct. (And in the end, they said, "Oh, this is a known issue--here's the patch." And then the patch didn't work when we tried it and we had to get another patch.)
Now, I have an issue that is excatly the opposite. The field is NULL in the database, but when the record gets read into the bean , the NULL value is not translated to the bean. Instead, the bean retains whatever information was there from the last use of that bean. I have contacted Bluestone again, but basedon the last response time, I'm not overly hopeful of a quick resolution.
Has anybody had these issues before? Is there an easy fix? I'm thinking of switching the beans over to BMP so that I can control the persistance and not rely on Bluestone's apparently shaky CMP, but before I do that I was wondering if there was anything simple to do.