In tomcat web container spring listens to session and executes a destroy-method on a "session-scoped" bean, that invokes a web-service.
sometimes this strange exception is raised:
interface com.sun.xml.ws.developer.WSBindingProvider is not visible from class loader
What can this mean?
This has to be a jar conflict issue. Check the below link if it helps:
generated-client-error
Regarding the issue "interface com.sun.xml.ws.developer.WSBindingProvider is not visible from class loader", the same issue has been envounterd when developping 3rd party h2h connection under the GlassFish Server v2.1 . But after moving the 3rd party related jar from ".../lib/ext” into the “.../lib” level this issue possible to be rectified.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.