[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1562714557 Has anybody looked into this? XML-Processing does not work in Camel-K until this is fixed. If there is anything I can do, plz let me know. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1527421259 I am 99% positive this not related to the dependencies in the camel component but to the old JAXP way to instantiate the XML processor/XSLT factory. JAXP relies on some really weird reflection stuff to instantiate the XML processing components. This seems to be a source of problems for Quarkus (see quarks/quarkus #1769)[https://github.com/quarkusio/quarkus/issues/1762]. I am not sure why Saxon version 10 works but version 11 doesn't but I assume that some JAXP related stuff was removed from Saxon 11. Or Quarkus since tokenize seems to be affected, too. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1523739914 We have analyzed the issue further: 1.) The described workaround works for the xslt-saxon component but it does not work for the xtokenize splitter. I will complain about a missing XPathFactory. I have not found out which dependency to add to fix that. 2.) This is related to the upgrade of Saxon from 9.9 (?) to version 11.4 during the 1.12. We have currently downgraded to Camel-K version 1.11.1 which ships with Saxon 9.9 and xslt-saxon and tokenize both work in that version. However, we need XSLT 3.0 features (xsl:evaluate) so we are currently adding a dependency on net.sf.saxon:Saxon-HE:10.9. This works for the moment but is a bit hackish. If I do find the time I will upgrade Camel-K to 1.12 again and see if I can downgrade Saxon to 10.9. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1520257396 Than I am completely clueless. But since the error will occur upon any xxslt-saxon usage it would surprise me if I was the first one to notice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1520242709 We are running 1.12.0. I am 99% sure this worked just fine until last week. Is it possible that there is some change in the base image? The Xerxes decencies reminds of old endorsed Sun nonsense that somebody finally might have kicked out of the Java image -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1520117765 If I add just the Xerces dep it will complain about another FactoryConfigurationError `com.ctc.wstx.stax.WstxInputFactory not found`. If I add a manual dependency on `woodstox-core`it will run. So my total command line looks like this: kamel run -d mvn:xerces:xercesImpl:2.12.2 -d mvn:com.fasterxml.woodstox:woodstox-core:6.5.1 test3.groovy --dev This is kind of a work around. But what actually surprises me is this: What has changed in the last week? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1519709213 I can confirm: Same thing happens on a completely new camel-k installation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [camel-k] fhossfel commented on issue #4266: [Regression] javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
fhossfel commented on issue #4266: URL: https://github.com/apache/camel-k/issues/4266#issuecomment-1519703403 No, I have not removed any dependency. I don't even know how do that. I run the integration like @lfabriko did: `kamel run myintegration.groovy --dev` I can try to reinstall the operator and see if the problem persists. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
