Hi ,
how to create CompositeUserType, that has CompositeUserType attribute?

Example:

public class AUserType implements CompositeUserType {
public Class returnedClass() {
return A.class;
}
}

public class BUserType implements CompositeUserType {
public Class returnedClass() {
return B.class;
}
}

class A{
B b;
}

class B{

}

class EnclosingClass{
A a;
}


How can I "flatten" all data of all those classes(EnclosingClass,A,B) in table EnclosingClassTable?

There are no examples.

Please, help.

wut? http://www.hibernate.org/ForumMailingli ... AskForHelp

That means:
how can I enforce hibernate to put all data of classes EnclosingClass, A, B into single table?

In simplest words:

is it really possible to create tree of CompositeUserObjects(that one is parent for other...), and then save entire tree in single table?

I did not find similar situation in tutorials and in docs.

I somehow doubt it. Ask Max.
Hibernate isn't the magic bullet solution people seem to think it is. Sure you can do plenty with it, and it's fairly flexible, but it won't do every crazy thing you can posibly think of.
Why would you want to save an entire tree in one table? That's not very OO or Normalised. If you go against core princibels like that then you're not going to get on very well with Hibernate.

It is not against core principals.

I have requirement to "flatten" all data from 2 objects: A and B in single table, when A "has" B.
Note: there is no requirement to flatten A that "has" COLLECTION of Bs.
So no principals violation.

And I supposed to gain this possibility from Hibernate almost free of charge, because it is looks like CompositeUserType is built for that, but unfortunatelly it able to work only down to simple types in CompositeUserType , not to attribute, that is CompositeUserType itself.

It would be nice to have that feature, but It seems we have not this one.
Thanks for answering, but it seems to me you did not understand completelly my question.
Thanks.

Why not simply store the data in 2 tables? One referencing the other...

It's given by God(business decision).
But It seems to me even if I have this agreement to use separate tables, UserType would not help.Right?