Java Class Access from Default Package
When collaborating on a Grails project, you may need to access a searchable Groovy object placed in the default package from a Java class in a named package. However, this poses a question: how can this be achieved?
Unlike in J2SE 1.4, Java no longer allows importing classes from the default package. To access a default package class from a packaged class, the default package class must be moved into its own package.
If you have access to the source generated by Groovy, you will need to post-process it to move the default package class into a dedicated package and add the "package" directive at the beginning of the file.
However, please note that JDK7 and JDK8 have introduced an even stricter prohibition against importing from unnamed packages. According to the JLS, the type name must belong to a class type, interface type, enum type, or annotation type that is either a member of a named package or a member of a type whose outermost lexically enclosing type is a member of a named package.
Why does the default package exist? It is intentionally provided by Java as a convenience for developing small or temporary applications or for initial development stages.
The above is the detailed content of How Can I Access a Groovy Class in the Default Package from a Java Class in a Named Package?. For more information, please follow other related articles on the PHP Chinese website!