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.

Sign up for GitHub

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

Jump to bottom

NestedSet & Play! framework model #3

Open
poum opened this issue Sep 16, 2011 · 1 comment
Open

NestedSet & Play! framework model #3

poum opened this issue Sep 16, 2011 · 1 comment

Comments

@poum
Copy link

poum commented Sep 16, 2011

I've tried to use JPANestedset which seems great and perfectly respond to my need but Play! model uses long ID and NodeInfo int ID..... I'm not a Java GURU and I don't know workaround to inherit from Play model & implement NodeInfo in the same time ...

But, is an int ID enough ? Should not a long better suitable for this need ?

PS: great work & many thanks
PSPS: sorry for my english :-(
@JustinTArthur
Copy link
Contributor

The solution might be to have the NodeInfo interface to not enforce the id field, instead relying on the JPA API to derive information about the id field—by no means a bad thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@poum @JustinTArthur