You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2022/09/03 11:01:00 UTC
[jira] [Updated] (CAMEL-17601) camel-core-model - Get rid of using JAXB
[ https://issues.apache.org/jira/browse/CAMEL-17601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-17601:
--------------------------------
Fix Version/s: 4.0
(was: 3.x)
> camel-core-model - Get rid of using JAXB
> ----------------------------------------
>
> Key: CAMEL-17601
> URL: https://issues.apache.org/jira/browse/CAMEL-17601
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 4.0
>
>
> JAXB is a pain for the the legacy XML DSL (spring <beans> and blueprint XML).
> Also JAXB is no longer in the JDK and its heavy to use.
> We have the new fast XML IO parser that we use for modern Camel apps.
> We should find a way in the future to get rid of JAXB in the core model and use a different way of generating the XML XSD.
> The current generator with some legacy maven plugins that generate JAXB -> XML Schema is brittle and will be in the future with modern JVM versions.
> Today we hit problems with this where generating OSGi XML does not work but it works for Spring XML.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)