Hello Mark. I made hibernate.param was deprecated in favor of generator-param and typedef-param. Sorry seems that I missed param usage for 'type' tag.
I will add type-param and tests in a few minutes. Thanks for your feedback. On 6/2/05, Mark Lundquist <[EMAIL PROTECTED]> wrote: > > Hi! > > OK, the Hibernate tags reference for Xdoclet2 leads me to believe that > it supports the Hibernate 3 ParameterizedType interface: > > <property name="foo"> > <type="com.bar.Foo"> > <param name="something">whatever</param> > </type> > <property> > > I don't think Xdoclet 1.2.3 supports those! Right? > > So, I've spent the morning getting Maven installed, getting Xdoclet2 > together, converting my Ant build to use Xdoclet2, changing > incompatible Xdoclet+Hiberntate tags... and I've just about got things > working. > > Except for the thing that precipitated my switch to Xdoclet2... :-/ > > I have this: > > /** > * @hibernate.property > * @hibernate.type > * name="us.rocketsurgery.hibernate.enumeration.EnumUserType" > * @hibernate.param > * name="class" > * value="com.wrinkledog.klamath.model.membership.Member.Status" > */ > > and I get this: > > <property name="status"> > <type name="us.rocketsurgery.hibernate.enumeration.EnumUserType"/> > </property> > > The next thing that happens is that Hibernate's schemaexport task barfs > with an NPE. If I add the <param> element to the mapping by hand, the > schemaupdate makes it past this point. > > So... What's the proper way to use the @hibernate.param tag for a > UserType in Xdoclet2? I presume that is the right tag to use (the > documentation seems to suggest it...)? Or if it's not, then what do I > do to get the mapping I'm after? > > HeeeeeEEEEEEeeeelp! > thx, > —ml— > > > -- anatol
