gnodet commented on issue #849: Support for camel-xml-io URL: https://github.com/apache/camel-quarkus/pull/849#issuecomment-595664601 > > > ``` > > > * If camel-xml-jaxb support and camel-xml-io are there for parsing routes from XML, their pom.xml descriptions (and yaml metadata) should say so. I do not understand them as a general purpose XML parser and a general purpose JAXB package. They are there for end user apps that require parsing routes from XML. They are not there for other Camel Quarkus extensions to get a general XML support (we may need to add new/adapt existing extensions for that). Right? > > > ``` > > > > > > Not really, `camel-xml-io` contains an xml parser implementation as far as i know > > Yes, there is a parser implementing Camels own interface `org.apache.camel.xml.io.XmlPullParser` and no other Camel component depends on it except for the core part that parses the XML routes. So, for me this does not look like a general purpose parser ATM. Is it supposed to become one in the future? > The goal is not to make the parser public. If other parts/components need a lightweight parser, why not, but it should be part of a public API for users. The only goal was to avoid having the dependency on the whole JAXP stack, but if users actually need to process XML data, it's safer to get the usual public API/ implementations.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
