[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351701#comment-14351701
]
Bryan Pendleton commented on DERBY-6773:
----------------------------------------
According to http://docs.oracle.com/javase/tutorial/deployment/jar/sealman.html,
the sealing violation means that you got org.apache.derby.impl.jdbc classes into
multiple Derby jar files.
Can you open up each of your Derby jar files using your system 'zip' utility and
look inside, and see which jar files have org.apache.derby.impl.jdbc classes
in them? They should only be in derby.jar, but are somehow in multiple jars.
Alternately, it could be that you have two different copies of the Derby jar
files
in your CLASSPATH. That is a common way to get the Sealing Violation.
> Derby throws plain SQLIntegrityConstraintViolationException
> -----------------------------------------------------------
>
> Key: DERBY-6773
> URL: https://issues.apache.org/jira/browse/DERBY-6773
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.10.2.0
> Environment: Windows 7 x86_64, Java 1.6.0.45
> Reporter: Jochen Wiedmann
> Assignee: Abhinav Gupta
> Priority: Minor
> Attachments: DERBY6733Repro.java, SamePackage.diff, ant -verbose
> build all.txt
>
>
> If a unique constraint is violated by an insert statement, then Derby throws
> an SQLIntegrityConstraintViolationException. The error message contains, in
> particular, the constraint name and the table name.
> To distinguish between cases with various constraints, Derby should instead
> throw a subclass of SQLIntegrityConstraintViolationException, with methods
> like getConstraintName(), and getTableName().
> See also https://hibernate.atlassian.net/browse/HHH-9516.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
