Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 843798, 1 year ago
interface dbtest.face is not visible from class loader
via felix-users by Andrea Turbati, 1 year ago
interface com.sun.xml.internal.ws.developer.WSBindingProvider is not visible from class loader
via osdir.com by Unknown author, 1 year ago
interface com.sun.xml.internal.ws.developer.WSBindingProvider is not visible from class loader
via apache.org by Unknown author, 2 years ago
interface com.sun.xml.internal.ws.developer.WSBindingProvider is not visible from class loader
via openejb-users by Wilingson, 1 year ago
interface org.apache.openejb.client.EJBObjectProxy is not visible from class loader
via osdir.com by Unknown author, 1 year ago
interface com.sun.xml.internal.ws.developer.WSBindingProvider is not visible from class loader
java.lang.IllegalArgumentException: interface dbtest.face is not visible from class loader	at java.lang.reflect.Proxy.getProxyClass(Proxy.java:331)	at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:552)	at dbtest.MyProxy.main(MyProxy.java:28)