You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a overriden RMIClassloader. It was working fine with Spring boot 1.3.x.
It puts a file into:
META-INF/services/java.rmi.server.RMIClassLoaderSpi
this file goes in in the fat jar in the root META-INF.
The class end up inside the application classes and is invisible for the system classloader.
If I put the class file manually along the org\springframework\boot\loader\ it works.
I understand, its not possible to make application classes visible to the system classloader (and this issue is similar to the problem with custom CharsetProvider).
Is it possible to modify the build process to put abitary classes or jar files (exploded) along the loader classes?
The text was updated successfully, but these errors were encountered:
Hi!
I use a overriden RMIClassloader. It was working fine with Spring boot 1.3.x.
It puts a file into:
META-INF/services/java.rmi.server.RMIClassLoaderSpi
this file goes in in the fat jar in the root META-INF.
The class end up inside the application classes and is invisible for the system classloader.
If I put the class file manually along the org\springframework\boot\loader\ it works.
I understand, its not possible to make application classes visible to the system classloader (and this issue is similar to the problem with custom CharsetProvider).
Is it possible to modify the build process to put abitary classes or jar files (exploded) along the loader classes?
The text was updated successfully, but these errors were encountered: