Question

I have developed a Java Application that connects with a database (insert, select …) with Apache Derby as DBMS, this appication is running fine on NetBeans, but when I export it in a Jar, and I run it outside without NetBeans, I receive this error:

after running this command:

 java -jar jarre.jar

I get this list:

I want my application to be portable, without starting NetBeans.
I know that I am missing something, but exactly what, is something I want someone to put light on?

Answer 1

Derby is an ex-IBM product and they are a bit fanatic about security (which can be good or bad). In your case, the Derby database uses the Security Manager API to make sure a lot of things are “safe”. See the documentation how to properly configure your security manager on the Derby Server.

The second option is to disable the security; don’t install a SecurityManager in your client.

I once spent roughly a week to set everything up correctly. This seems odd because Derby supplies example security files. The problem is that once you install a SM, it applies to everything

So you might need to change code in non-Derby parts, write more extensive policy files for those parts of the code and do a lot of ugly stuff that is scarcely documented. I didn’t like it. For the most part, it felt like stabbing in the dark.

Disabling the security is often the preferred option unless your code was written with security in mind from the ground up (and all frameworks that you use, too).