Re: [smartweb-devel] Smartweb Auth and problem with XDoclet/ Hibernate union subclass

[Gaetano P. <gpe...@sm...>]

I delve into the problem and hibernate documentation says that identity
generator strategy is not allowed in union subclass inheritance, indeed the
primary key seed has to be shared accross all unioned subclasses of a
hierarchy.
The suggested approch for generating table  for concrete class is to use a
sequence generator strategy instead of native.  With this approch each table
defines columns for all properties of the class, including inherited
properties. The limitation of this approach is that if a property is mapped
on the superclass, the column name must be the same on all subclass tables.
(Hibernate group is going to relax this in a future release).
This means that a dedicated class tree sequence could be
introduced....Otherwise i don't know what happens using the
hibernate_sequence as sequence instead of generator native...
What do u thing about it??


svetrini wrote:
> 
> At this time smartweb auth  has a little problem... Actually union
> subclass has.
> hbm generation fails due to a bug on xdoclet union subclass.
> We have just sended patches to xdoclet team but none new version was
> released.
> I recently found another minor problem on auth module. It doesn't create
> schema on dbs different from PostgreSQL ( I tried on MySQL and HSQL ) this
> is not our bug but a knowed hibernate  problem.
> 
> So...
> 
> What do you think about change from union subclass to another subclass
> type?
> 
> I'm waiting to your answers... :-)
> 

-- 
View this message in context: http://www.nabble.com/Smartweb-Auth-and--problem-with-XDoclet--Hibernate-union-subclass-tf4761003s17546.html#a13624965
Sent from the SmartWeb Developers mailing list archive at Nabble.com.