Hi Jared
On Thu, Dec 10, 2020 at 7:49 PM Jared Whiklo <jwhi...@gmail.com> wrote:
> Well played Zoran, well played.
Thanks :) We aim to please :)
> Ok as I wait for IntelliJ to finish digesting Camel I have two follow-up
> questions
Oh, I hope you didn't try to import the whole project, I usually just
open the modules I work on, also have a look at mvnd[1] if you're
rebuilding, it does speed up things considerably.
> 1. Digging in some more, perhaps this is more my expectations.
snip
> But
>
> .to("xslt:{{xslt.path}}/FOXML.xslt?transformerFactory=#xsltTransformer")
>
> results in
>
> .to("xslt:classpath:/FOXML.xslt?transformerFactory=#xsltTransformer")
>
> instead of the expected
>
> .to("xslt:file:/tmp/FOXML.xslt?transformerFactory=#xsltTransformer")
To me that looks like {{xslt.path}} was replaced with an empty string,
and then the XSLT component assumes that the FOXML.xslt is on
classpath. Perhaps logging `{{xslt.path}}` would show this to be true.
And, as a workaround you could try `${properties:xslt.path}` instead?
> Using Spring Boot means it auto-configures a property parser and my own
> causes a conflict.
>
> I can use @PropertyInject to inject all the properties and then rewrite
> the above as
>
> .to("xslt:" + XSLT_PATH + "/FOXML.xslt?transformerFactory=#xsltTransformer")
>
> but I wanted to check that I was not missing something obvious.
There might be a bug in there with refactoring/optimizations we did
around this on 3.x, perhaps CAMEL-14445 not sure, Guillame or Claus
can you chip in?
> 2. Is there documentation on how to test the adoc production (I've
> never used adoc before) so I don't make ugly pages edits?
Glad you asked :) There is a README in camel-website[2] repository. A
TLDR for what you're after is checkout the website, configure
`antora-playbook.yml` to point to your local git clone[3] and run
`yarn preview` and rebuild the documentation with `yarn
build:antora`[4].
Make sure you have the correct version of NodeJS[5].
If you find that too complicated just create a PR if it looks okay
we'll merge and see the results on the website in a couple of minutes.
There is a possibility that we break something, but we can fix it in
the next couple of minutes also, and it's already broken so try not to
worry too much about that.
zoran
[1] https://github.com/mvndaemon/mvnd
[2] https://github.com/apache/camel-website/
[3]
https://github.com/apache/camel-website/#working-on-documentation-asciidoc-content
[4] https://github.com/apache/camel-website/#preview-website-locally
[5] https://github.com/apache/camel-website/#node
--
Zoran Regvart
