I have what I would consider an extremely odd issue.  I'm encoding a byte[] using Base64 into a container managed field.  I'm using Postgres as my back end database.  Everything works fine when the bean read/writes that byte[] array to the database (of course it's actually writing the encoded string to an OID field in the back end table).  Now the problem, if I re-deploy the bean ALL the byte[] get changed to something odd that's only 6k, when they were 12k-14k before the re-deployment.  All the other fields in the table remain untouched.
 
I've inserted debug code into the bean and it doesn't appear that ejbStore() is getting called, which should be the ONLY place a db write is occurring.  I don't see anything funny in the server.log that would indicate the database is being modified?
 
Any ideas??
 
--Scott

Reply via email to