While I'm creating this object model I ran into an issue.

I'm using Liferay and they have their own user object. This user object does not contain hibernate validation (and it shouldn't). What would be the most appropriate design decision to add validation into the application?

So far it has been using a facade to add the validation parameters onto the getters. It just seems like it gets overbearing and big, does anyone else have a better way to add validation onto objects that you don't have control over?

I guess I could make a translation service/object to go back and forth between the two? Haven't tried it yet, but maybe it would feel less complicated.

Hi,

so your problem is that you cannot place validation annotations onto the entities, right? Have you considered xml configuration? This allows you to add constraints to classes you cannot modify.

--Hardy

*clap clap clap* :$

You know, for some reason that never crossed my mind. Ofcourse we can use something else besides annotations when the process calls for it. Down with annotations, long live the xml file!

Thanks a bunch yo.