We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reviewing the spec, I'm wondering whether we should revise some restrictions on user code.
@Entity
An entity class must:
final
public
protected
But this leads me to wonder why static inner classes are prohibited?
static
@Embeddable
Embeddable classes have the same restrictions as entity classes.
But I would have expected that an embeddable class should be non-abstract.
abstract
And I don't see any reason why static inner classes should be prohibited.
A primary key class must:
Why must a primary key class be public when we don't apply this restriction to embeddables?
Is the requirement for serializability really necessary? (Yes, I remember where this came from, but I don't believe it's relevant anymore.)
Surely a primary key class should always be non-abstract.
The text was updated successfully, but these errors were encountered:
revise restrictions on entity/embeddable classes and primary key classes
8945cad
see jakartaee#380.
revise restrictions on entity/embeddable classes and primary key clas…
99c6d3e
…ses (#428) see #380. Co-authored-by: Lukas Jungmann <lukas.jungmann@oracle.com>
No branches or pull requests
Reviewing the spec, I'm wondering whether we should revise some restrictions on user code.
@Entity
classesAn entity class must:
final
public
/protected
)public
/protected
But this leads me to wonder why
static
inner classes are prohibited?@Embeddable
classesEmbeddable classes have the same restrictions as entity classes.
But I would have expected that an embeddable class should be non-
abstract
.And I don't see any reason why
static
inner classes should be prohibited.Primary key classes
A primary key class must:
public
public
)public
/protected
Why must a primary key class be
public
when we don't apply this restriction to embeddables?Is the requirement for serializability really necessary? (Yes, I remember where this came from, but I don't believe it's relevant anymore.)
Surely a primary key class should always be non-
abstract
.The text was updated successfully, but these errors were encountered: