microsoft / microsoft/kiota-java
Very old stax implementation causes Error in relation with quarkus and Hibernate
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 38
- Forks
- 34
- Avg merge
- 15h 9m
- Merged PRs (30d)
- 20
Description
I have different Quarkus projects which use com.microsoft.graph:microsoft-graph and io-quarkus:quarkus-hibernate-orm. After upgrading microsoft-graph to >= 6.30 i always get this error:
> Runtime java.lang.RuntimeException: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
> [error]: Build step io.quarkus.narayana.jta.deployment.NarayanaJtaProcessor#build threw an exception: javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found
After some painfull investigations i come arround that the solution was for me to exclude javax.xml.stream:stax-api which is come from this lib.
I am a little bit confused you ship a lib which is developed in 2008. I think it comes from this issue (https://github.com/microsoft/kiota-java/issues/1755), but isn´t there a better solution?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing which dependency brings javax.xml.stream:stax-api into projects using microsoft-graph version 6.30 or later, then reproduce the failure with Quarkus and Hibernate ORM. Done means the provider error no longer occurs without requiring users to manually exclude stax-api.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100