I have a unique component in which I'm attempting to persist a instance of an interface with no Setter methods. Is this a possiblity?

Scott

You can persist pretty much anything using custom PropertyAccessors and UserTypes

I just noticed the PropertyAccessor interface and I figure that I can create an implementation that returns a mock setter (i.e. one that doesn't do anything).

Without a deep understanding of Hibernate, I don't know what implications this might have. Are there any pitfalls that I'm going to run into?

Scott

a mock setter?

hibernate uses the returned Setter instance to "inject" the property values into your object model.

so a setter that did nothing would mean you'd get back an object which had no set value for that property.

This particular object is to be write only. In other words, it's the resposibility of another system to read the records.