OSUser and Hibernate

As promised, I have started work on Conductor but have not checked 
anything in yet.  One of the issues I am currently tackling deals with 
the the use of OSUser and Hibernate.  I am soliciting people's opinion 
regarding this, especially Mike CB since Confluence (I believe) is 
using both of these.

If I use the Hibernate provider for OSUser, everything is perfect.  I 
can have one-to-many/many-to-many relationships between the OSUser 
object and other objects.  For example, an OSUser object can have an 
address object.  This allows me to use Hibernate's OQL and everything 
else.  The problem comes when I decide not to use the Hibernate 
provider.  For example, I use the LDAP provider to integrate into an 
existing environment.  All the mappings I previously had are not longer 
applicable (unless I turn on cascading to the OSUser object which is 
possible a bigger issue).

Therefore, what is the best way to maintain relationship between the 
OSUser object and it's related objects when using Hibernate (or any 
relational tool for that matter)?


Cheers,
   matthew



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf