We have found the problem, we think. The ActiveMQ project uses derby and contains the contents of derby.jar in it's activemq.jar file.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 12 April 2007 12:29 To: Derby Discussion Subject: Re: Problems with Derby 10.2.2.0 Andrew Norman wrote: > I have a series of unit tests for our application. Due to issues with > the metadata, I have upgraded to the latest official release (10.2.2.0) > and have started getting the following error message appearing in my tests. > > Caused by: java.lang.SecurityException: sealing violation: package > org.apache.derby.iapi.services.crypto is sealed [snip] > Any ideas on what I should look at. Such sealing violations usually happen when classes in the same Java package are attempted loaded from different sources (jar files). Please double check that you don't have multiple versions of the same jar files in your classpath, especially multiple derby.jar files. -- John
