Very old stax implementation causes Error in relation with quarkus and Hibernate
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- backend, build-system
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.
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?
- Dominant language
- Java
- Stars
- 38
- Forks
- 34
- Avg merge
- 14h 29m
- Merged PRs (30d)
- 22
Getting set up
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.
More from microsoft/kiota-java
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/kiota-java#2127 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/kiota-java#2000 ·
Maintainers usually reply within 1 day
-
upgrade to okhttp 5Openenhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoft/kiota-java#1984 · 10 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
enhancement help wanted type:enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/kiota-java#1685 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/kiota-java#1612 ·
Maintainers usually reply within 1 day
All issues in microsoft/kiota-java
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/notes-android#3367 ·
Maintainers usually reply within 1 day
-
:wave: team-triage a:chore in:isolated-projects in:kotlin-dsl
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day