Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 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
- 545 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K 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
- 440 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
Prevention of interpretation of interfaces

How can you prevent interfaces from being Interpreted in java
interface A{ int x;
double addPrice(double a,double b);
}
how to stop interface A from being Interpreted
Answers
-
How can you prevent interfaces from being Interpreted in javainterface A{ int x;double addPrice(double a,double b);}how to stop interface A from being Interpreted
The only way I know is: DON'T USE IT.
Don't implement it in classes and don't include it in the classpath when you compile.
Other than that why would you have it to begin with if you don't want it to be used?
WHAT PROBLEM are you trying to solve?
-
What do you even mean by "interpreted"?
I guess you're talking about decompilers? There's only one way and that's never to distribute your compiled classes.
And why'd you want people to not be able to decompile your interfaces anyway? It makes no sense, there's nothing in there that'd in any way be helpful beyond what decent documentation already provides (or shouldn't be, I know some people put method implementations in interfaces now).