In our application, using blobs works just fine when we use save(). However, when we use merge(), we get a null on nult null field exception. After tracing through Hibernate, I discovered that org.hibernate.type.Blob.replace() does not copy the blob.

If I change the replace method to return 'original' instead of 'target' (target is always null) it seams to work just fine.

Should I log this as a bug in Jira?

As per the EJB3 spec
"Fields or properties of type java.sql.Blob and java.sql.Clob are ignored by the merge operation."
But we should not throw an y exception and we should explicit it in the doc if not yet. Post to JIRA with a detailed explicatation of you problem.
Thanks

That's too bad. Fortunately, though, I think I can work around this.

Thanks for the feedback.