-
Notifications
You must be signed in to change notification settings - Fork 6
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
com.ctc.wstx.stax.WstxOutputFactory not found when using Pact Provider #85
Comments
To confirm, is this with the What version of Java are you using? Does it work to add this dependency to your
(The 'correct' scope for that would be test, but please try it without test scope, because there's some other issues with the classloading of the test scope dependencies, and we don't want to confuse things.) |
We are running the quarkus-pact-provider extension. We are not running the contracts tests in the OpenShift image, but since the scope of the extension is not test, then the extension will be packed in the image and there for seams to cause som problems for us. I could change the scope of the quarkus-pact extension to test and it will probably work, but then the test won't (as the other issue) work in Dev-mode and we really want that :) We are currently running Java 11, OpenJDK. Adding that Woodstock-core didn't solve the problem, now we got this error:
I will try to build with the quarkus-pact-provider in test-scope and see if it works better. |
Thanks for confirming! I have a pretty good idea why you're getting the As well as trying By coincidence, I'm just looking at some changes that would allow us to get rid of the whole code path involved in the |
No problem, thanks for helping out! I will describe the situation better :) When I said that the test wont run, i meant that the test won't run in Dev mode, but if I I did an build with the provider extension in test-scope and and it worked in my Openshift envirement, so It seams that dependency of the provider extension adds some dependency that makes stuff brake, but I maybe wrong :) This microservice uses a lot of JAXB, XML and generating JAXB-classes from schema files, so thats why we have so much of this. I tried to scope of the extension to provided, but that broke our schema generation that we do at compile-phase in Maven. The error that I get is
|
I think I have an idea how to fix this, but it will require JUnit 5.10, so it's a ways off, unfortunately. |
Hi!
When we are using the Pact Provider and it works great while we develop and run our microservice local, but when we run it in an image at Openshift, we get this error massage:
If we remove the Pact provider dependency, it will start working.
Quarkus version: 2.15.0-Final, have tried the 2.16.3-Final with the same result.
The text was updated successfully, but these errors were encountered: