Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Fixing start issues - certificate - self-signed certificate

Hi,
for my master thesis I developed a medical client-server-application in bioinformatics with Java. I will write a scientific paper for a publication in a journal.
Therefore, for the scientific opinion, the application has to work and start properly. It must be ease for a user to execute the application without requesting the user to change his Java runtime security settings. An execution might not be certain, after a Java update an execution of the JAR file or a webstart could be denied. A start must be reliable and user-friendly. Otherwise my paper will not be accepted and the application will only be used by a few users.
I am originally a C# developer. Compared to .NET an execution of the application is not so easy.
After publishing Java requires a certificate for an execution. Creating one and signing one is an additional effort.
After that Java throws an exception because the certificate is self-signed.
It is a lot to do to fix or avoid restrictive issues.
How can I fix that exception so that a start might be no problem for a user?
Would later Java versions still allow an execution?
Best wishes