New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not hardcode the TransformerFactory implementation irreversibly #1017
Comments
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 2, 2020
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 2, 2020
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 2, 2020
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 2, 2020
ppalaga
added a commit
that referenced
this issue
Apr 2, 2020
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 3, 2020
ppalaga
added a commit
to ppalaga/camel-quarkus
that referenced
this issue
Apr 3, 2020
ppalaga
added a commit
that referenced
this issue
Apr 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After this change 9af2546#diff-e4d998f8f2cd322095bf13aad3daff36R26-R37 there is no way for the user to change the effective TransformerFactory implementation if it does not work for him. We should figure out a less intrusive and better maintainable way of promoting our TransformerFactory.
A PR follows.
The text was updated successfully, but these errors were encountered: