hibernate-devel

[Hibernate] CodeGenerator bug

[Gavin K. <ga...@ap...>]

This bug is still in the current codebase:

    public SubDetai) {
    }

I had been under the impression it was fixed already..... I know someone
else knew what was going on there....

Re: [Hibernate] CodeGenerator bug

[Max R. A. <ma...@eo...>]

Yes - it was the problem about creation of the minimal constructor in the
codegen.

Which hbm.xml are you running it on ?

/max

----- Original Message -----
From: "Gavin King" <ga...@ap...>
To: <hib...@li...>
Sent: Thursday, October 31, 2002 6:37 PM
Subject: [Hibernate] CodeGenerator bug


> This bug is still in the current codebase:
>
>     public SubDetai) {
>     }
>
> I had been under the impression it was fixed already..... I know someone
> else knew what was going on there....
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

Re: [Hibernate] CodeGenerator bug

[Max R. A. <ma...@eo...>]

Ok - I've found the exact problem.

The hbm.xml file does not state a type for any of the property names in the
SubDetail class - thus the codegenerator
cannot give it any sensible class name (maybe we should just insert
java.lang.Object or java.lang.String then ?)

The codegenerator assumes there are at least ONE attribute on each
persistent class, and in this case it sees none
because of the above mentioned "error".

I can easily fix the problem of an incomplete constructor, but it will only
hide the true error - that
you have not created a hbm.xml that can be codegenerated (except if we add a
new feature to the codegenerator to
insert af default java type for properties without a type?)

/max

----- Original Message -----
From: "Gavin King" <ga...@ap...>
To: <hib...@li...>
Sent: Thursday, October 31, 2002 6:37 PM
Subject: [Hibernate] CodeGenerator bug


> This bug is still in the current codebase:
>
>     public SubDetai) {
>     }
>
> I had been under the impression it was fixed already..... I know someone
> else knew what was going on there....
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future
> of Java(TM) technology. Join the Java Community
> Process(SM) (JCP(SM)) program now.
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

Re: [Hibernate] CodeGenerator bug

[Gavin K. <ga...@ap...>]

> The codegenerator assumes there are at least ONE attribute on each
> persistent class, and in this case it sees none
> because of the above mentioned "error".

Theoretically Hibernate can persist a class with no properties ...
CodeGenerator should handle the *possibility* at least.

> I can easily fix the problem of an incomplete constructor, but it will
only
> hide the true error - that
> you have not created a hbm.xml that can be codegenerated (except if we add
a
> new feature to the codegenerator to
> insert af default java type for properties without a type?)

Nah, lets not assume any default property types.

Re: [Hibernate] CodeGenerator bug

[Gavin K. <ga...@ap...>]

Thanks Max :)

----- Original Message -----
From: "Max Rydahl Andersen" <ma...@eo...>
To: "Gavin King" <ga...@ap...>
Sent: Sunday, November 03, 2002 1:13 AM
Subject: Re: [Hibernate] CodeGenerator bug


> > > The codegenerator assumes there are at least ONE attribute on each
> > > persistent class, and in this case it sees none
> > > because of the above mentioned "error".
> >
> > Theoretically Hibernate can persist a class with no properties ...
> > CodeGenerator should handle the *possibility* at least.
>
> I've submitted a small patch that handles that *possibility*
>
> > > I can easily fix the problem of an incomplete constructor, but it will
> > only
> > > hide the true error - that
> > > you have not created a hbm.xml that can be codegenerated (except if we
> add
> > a
> > > new feature to the codegenerator to
> > > insert af default java type for properties without a type?)
> >
> > Nah, lets not assume any default property types.
>
> Thus the codegenerator will still generate  a class, but it will not
contain
> properties without
> provided types..
>
> /max