You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2009/11/12 09:17:39 UTC
[jira] Resolved: (OPENJPA-1046) Unique Constraint on
MappedSupperClass causes NullPointerException
[ https://issues.apache.org/jira/browse/OPENJPA-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar resolved OPENJPA-1046.
------------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.0)
2.0.0-M4
Commits are wrongly tagged as OPENJPA-1047
> Unique Constraint on MappedSupperClass causes NullPointerException
> ------------------------------------------------------------------
>
> Key: OPENJPA-1046
> URL: https://issues.apache.org/jira/browse/OPENJPA-1046
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Fix For: 2.0.0-M4
>
>
> Defining UniqueConstraint on MappedSuperClass fails with NPE [1]
> @MappedSuperclass
> @Table(uniqueConstraints={@UniqueConstraint(columnNames={"ATTR_NAME", "OWNER"})})
> public abstract class Attribute<T> {
> While it is debatable a @Table annotation is appropriate for @MappedSuperClass, the situation must be detected and warned more gracefully than a NPE.
> Also investigate whether UniqueConstraint on a MappedSuperClass should be supported.
> [1] http://n2.nabble.com/UniqueConstraint-in-a-MappedSuperclass-not-working-tc2633410.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.