My SOAP service stopped working again. It seems if I wait a few months, something, the Java version, or something else will have changed and I have to basically start over (“Create a Web Service Project, …). I’m not sure why, but SOAP services seem extremely brittle.
This morning, trying to run the formerly-working SOAP service just gave ma a screen full of errors (again).
Here are some ones that apply to some illegal accesses that could be causing the errors — see below
Have these been resolved in recent builds?
Thanks,
—-
Trying to run the client….
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 (file:/Applications/MyEclipse%20CI/MyEclipse%20CI.app/Contents/Profile/plugins/com.genuitec.eclipse.ws.xfire_13.0.0.me201812061423/lib/webservices-rt.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
WARNING: Use –illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
=====
Trying to do a Maven build of the formerly-working project, gave me these errors:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 (file:/Applications/MyEclipse%20CI/MyEclipse%20CI.app/Contents/Profile/plugins/com.genuitec.eclipse.ws.xfire_13.0.0.me201812061423/lib/webservices-rt.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
WARNING: Use –illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
******
Java of late has been making some changes that are breaking some older applications, starting with Java 9. The issues you are seeing appears to be related to restricted access to internal APIs, something that would affect older versions of JAXB (part of the web services JAR). This is not something MyEclipse has much control over.
Unless you specifically need to move to a newer version of Java, the most expedient solution would be to not try and re-create the webservices, but checking the Java version you’re running with and going back to an earlier version. Just keep your existing code and change the version of Java it is running with.
As far as the JAXB issue itself is concerned, it looks like we’ll have to update the generation wizards in MyEclipse to create projects with more recent versions of the libraries which support Java 11+.
发表回复