-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File in META-INF/services has deprecated name #95
Comments
|
smillidge
added a commit
to smillidge/metro-saaj
that referenced
this issue
Nov 17, 2018
Signed-off-by: smillidge <[email protected]>
smillidge
added a commit
to smillidge/metro-saaj
that referenced
this issue
Nov 17, 2018
Signed-off-by: smillidge <[email protected]>
lukasj
pushed a commit
to lukasj/metro-saaj
that referenced
this issue
Nov 27, 2018
Signed-off-by: smillidge <[email protected]>
Tomas-Kraus
pushed a commit
that referenced
this issue
Nov 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had an application that was written back when J2SE included SAAJ, so of course it broke after upgrading from Java 8, and I grabbed jaxws-ri from Maven and put the necessary jars on the classpath and the application worked again, but with this warning:
The application calls
SOAPConnectionFactory.newInstance
andMessageFactory.newInstance
, ultimately causing theServiceLoader
to find theMETA-INF/services/javax.xml.soap.MetaFactory
file.I was able to make the warning go away by modifying
saaj-impl.jar
, simply extracting thejavax.xml.soap.MetaFactory
service file, deleting it from the jar, then re-adding it under the non-deprecated namejavax.xml.soap.SAAJMetaFactory
. With that, my application worked fine and gave no warning, though someone more knowledgeable than I will have to judge whether that's a fully correct fix.The text was updated successfully, but these errors were encountered: