-
Notifications
You must be signed in to change notification settings - Fork 869
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
Document Querydsl Roo support better #546
Comments
I am the person who reported this on Twitter :-). I am a beginner on Roo and over the past few weeks I've built a data model for a small case study I'm doing for my PhD. I don't mind sharing it if it helps find out something. Shall I? In short, I have a hierarchy of classes with @RooJpaEntity, some of which are extended with AspectJ ITDs. I don't really expect a source-based approach to pick up those ITDs, but it'd be nice if inheritance did work. |
Let me revise that a bit: I have a few @RooJpaEntity classes, but many more use @RooJpaActiveRecord instead. Isn't RooJpaActiveRecord a superset of RooJpaEntity, as stated in the javadocs here? I created most of my classes with the usual Roo commands and most of them don't actually use RooJpaEntity but RooJpaActiveRecord instead. |
Ok, then at least one improvement on the APT side could be to support both RooJpaEntity and RooJpaActiveRecord. |
Thanks, that would be great :-). |
Released in 3.3.0.BETA1 |
Document Querydsl Roo support better. The APT based approach works only if all the relevant data is on the source level (RooJpaEntity annotation and property declarations).
The text was updated successfully, but these errors were encountered: