Not a problem using the index attribute is what I was after thanks! guess 
thats another change from the XDoclet 1 syntax.

- Richard


>From: Konstantin Priblouda <[EMAIL PROTECTED]>
>Reply-To: xdoclet-plugins-interest@lists.sourceforge.net
>To: xdoclet-plugins-interest@lists.sourceforge.net
>Subject: Re: [xdoclet-plugins-interest] Problems specifying an 
>indexwithXDoclet2 hibernate plugin
>Date: Thu, 20 Jul 2006 08:06:55 -0700 (PDT)
>
>
>
>--- richard osbaldeston <[EMAIL PROTECTED]>
> >
> > If I remove the @hibernate.column then I end up with
> > the hbm looking like my
> > second example which fails to tell hibernate to
> > generate an index for the
> > column (I've checked the generated sql schema -
> > which at least worked). Are
> > index declartions done differently in XDoclet 2?
> > this property isnt a PK so
> > I need to declare it explictly.
> >
> > I'm guessing my use of @hibernate.index-column was
> > wrong then.
>
>certainly.  it is not used by many-to-one at all
>( you can always look into jelly template to see what
>is going on )
>
>And there is also index  attribute for many to one.
>It generates foreign key in any case ( to one side id
>)
>( please note I'm short before 3 week vacation and
>moving my provate webbserver to another host right now
>;) )
>
>
>regards,
>
>
>----[ Konstantin Pribluda http://www.pribluda.de ]----------------
>Still using XDoclet 1.x?  XDoclet 2 is released and of production quality.
>check it out: http://xdoclet.codehaus.org
>



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
xdoclet-plugins-interest mailing list
xdoclet-plugins-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest

Reply via email to