David, Apart from what Craig has suggested, what came to my mind is that there is an ongoing effort to implement JSR-303 Bean Validation in OpenJPA 2.0. Not sure however, whether it is sufficiently implemented yet and it can be used for your purpose. Might be worth checking though.
Cheers, Milosz > I realise that this is not strickly an OpenJPA problem, rather a more > general JPA one, but there are experts here who might know the answer. > > I have a number of classes which represent tables which have not only > an Id field, but also various other fields which are marked as unique. > > When I persist and then try to flush a new object which has a non-unique > value in the object (the user entered bad data) it breaks the transaction > and throws an error. All of which is quite understandable. > > The question is what is the best way to avoid it. Do I have to build the > checking into the application, or is there a more generic way which I > can use as a validation technique before I try to persist the object. > > David >
