-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cannot call Soap service with jax-ws #2188
Comments
Is it possible that the |
Hi @troosan
Is there any additional step I have to do? |
@jramirez-isc you might have to add a maven repository to your settings.xml <pluginRepositories>
<pluginRepository>
<id>smartbear-sweden-plugin-repository</id>
<url>http://www.soapui.org/repository/maven2/</url>
</pluginRepository>
</pluginRepositories> |
@troosan Adding the repository to
I also tried running in dev mode with
|
@jramirez-isc I added the missing mvnw files. But I'm not sure it will solve the first issue. |
@troosan Yes, the problem was my proxy settings. |
@jramirez-isc Thanks for the suggestion, I didn't know that tool. I also added another rest endpoint that calls a webservice exposed on the internet (might not work if you are behind a proxy). The endpoint is http://localhost:8080/vat/GB/391313073 which calls the VIES webservice (https://ec.europa.eu/taxation_customs/vies/checkVatTestService.wsdl). |
Hi @troosan, I see no errors when building it with GraalVM version 20.1.0. Can you please try that version?
This happens because the config for Also, make sure you specify all four config files in your
|
Hello @jramirez-isc, I have tried the above configurations as mentioned here for generating the native image and I was able to get past the above error by regenerating the config files using the filter and proceed further. However, I encountered another error
I have
I have also verified the contents of this file
Do you have any pointers or clues that I can use to continue investigating further? GraalVM version -> 20.1.0
|
I can confirm this problem persists even with Java 8.
|
Finally I got this working.. Had to switch to apache cxf ws implementation. Used the latest 3.4.0 plugin and include 2 libraries cxf-rt-frontend-jaxws, cxf-rt-transports-http. Regenerated the config files and finally able to invoke the Webservice. |
Thanks letting us know! |
However, I would like to point out that I had to resort to
|
Also, you will be having a tough time when using cxf security, which by default is now using ehcache, which itself is OSGI based... |
I'm actually surprised this was closed, as the issue is not fixed. |
So for now there is no way to successfully build a native image by using soap services with JAX-WS? |
Describe GraalVM and your environment :
report-unsupported-elements-at-runtime
)Run the following to capture compiler version
cl.exe
cc -v
gcc --version
Run the following to capture linker version
cl.exe
cc -Wl,-v
gcc -Wl,--version
java -Xinternalversion
:Have you verified this issue still happens when using the latest snapshot?
Not yet
Describe the issue
Calling a Soap service fails
Steps to reproduce the issue
I created a little test project to reproduce the issue. You can find it here:
Expected behavior
Service gets called successfuly
Additional context
When adding
--report-unsupported-elements-at-runtime
the build succeeds, but I get the following error at runtimwithout the option the error is similar
The text was updated successfully, but these errors were encountered: