ppalaga commented on issue #3904:
URL: https://github.com/apache/camel-quarkus/issues/3904#issuecomment-1180092910
> ref and bean URI will generate xslt templates dynamically at runtime. So I
think it could not be supported in native mode.
Yeah, those cases are harder, but still perhaps doable to some extent, as
long as the XSLT stuff is known at build time. Of course, if the user generates
XSLT resources dynamically at runtime, it won't work in native mode. But if he
only has a `@Named` singleton bean that he uses in a `ref` URI, then it could
perhaps work with some additional config or a new dedicated annotation,
something like `@XsltResource("foo/bar.xsl")`. Then we could scan for those
`@XsltResource` annotations at build time and simply replace `ref:beanName` for
`classpath:foo/bar.xsl`. Maybe if we had [buildtime routes introspection
API](https://issues.apache.org/jira/browse/CAMEL-16212) even the additional
config/annotation would not be needed.
I am not sure how much cases we could cover like this and I am not sure at
all whether this is worth the effort. Perhaps not at this time, we might have
more important things to do.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
