Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid code generated with Custom types and HibernateDomainExporter #237

Closed
mirkosertic opened this issue Sep 25, 2012 · 2 comments
Closed

Invalid code generated with Custom types and HibernateDomainExporter #237

mirkosertic opened this issue Sep 25, 2012 · 2 comments
Assignees

Comments

@mirkosertic
Copy link

@mirkosertic mirkosertic commented Sep 25, 2012

Hi there

the following code is generated in QGeschaeft for the persistent type Geschaeft:

    // custom
    public final Path<ZustandGeschaeft> zustand = new Path(forProperty("zustand"));

The Property zustand is of Type ZustandGeschaeft, which itself is not a persistent class, but mapped with a custom type. It is used to model the GoF State pattern, and does just contain logic. The instances of ZustandGeschaeft are stateless singletons. I thing a meaningful query could only be constructed by object reference, and not object values. There are other custom types causing the same compilation problem, but they have a value and persistent properties. Any ideas how to solve this problem?

@ghost ghost assigned timowest Sep 25, 2012
timowest added a commit that referenced this issue Sep 25, 2012
@timowest
Copy link
Member

@timowest timowest commented Sep 25, 2012

Custom types are now reflected as entity types. These entity types are empty though, because I am not yet sure how fields and properties of those should be handled.

@timowest
Copy link
Member

@timowest timowest commented Sep 29, 2012

Released in 2.8.0

@timowest timowest closed this Sep 29, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants