[
https://issues.apache.org/jira/browse/CAMEL-21286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885960#comment-17885960
]
Claus Ibsen commented on CAMEL-21286:
-------------------------------------
>From the camel source it looks like this classloader is only in use of JAXB
>classes has not been annotated with JAXB annotations and does not have
>jaxb.index files.
And this seems to require enabling this mode specially in camel via
FallbackTypeConverter#setObjectFactory(true) or via a camel global option
CamelJaxbObjectFactory
[https://github.com/apache/camel/blob/f0b4bb237331c5f9d595286dd0f2097cee8c43f7/components/camel-jaxb/src/main/java/org/apache/camel/converter/jaxb/FallbackTypeConverter.java#L141]
Can you check what your example are doing in this regard in Camel Spring Boot.
As this seems for a special use-case and we need to understand this better
before we can find a good solution.
> Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
> ---------------------------------------------------------------------------
>
> Key: CAMEL-21286
> URL: https://issues.apache.org/jira/browse/CAMEL-21286
> Project: Camel
> Issue Type: Improvement
> Components: camel-jaxb
> Affects Versions: 4.4.3
> Reporter: Adriano Machado
> Priority: Major
> Attachments: Screenshot 1.png, Screenshot 2.png
>
>
> Camel is calling `JaxbHelper.getJaxbElementFactoryMethod` and the result is
> not being cached. This expensive call on apps with schemas deployed on nested
> jars on Spring Boot apps running on Openshift.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
