Skip to content
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

Properies evaluation broken after the introduction of PropertyBindingSupport #129

Closed
ppalaga opened this issue Aug 12, 2019 · 5 comments
Closed
Assignees

Comments

@ppalaga
Copy link
Contributor

ppalaga commented Aug 12, 2019

The evaluation of properties does not work after a76c752 "chore: replace custom properties binding implementation with PropertyBindingSupport from camel support".

Reproducible through building the Twitter itest and running the jar manually. Clearly the twitter credentials need to be set as documented in the itest README. The scenario succeeds before a76c752 and fails after a76c752.

Please assign to me.

@lburgazzoli
Copy link
Contributor

@ppalaga done, please create a test against core too so we can isolate where the problem is

@ppalaga
Copy link
Contributor Author

ppalaga commented Aug 12, 2019

There is trailing period missing at

Let me figure out how to test that.

@lburgazzoli
Copy link
Contributor

lburgazzoli commented Aug 12, 2019 via email

@lburgazzoli
Copy link
Contributor

you can test it by setting:

camel.component.timer.resolve-property-placeholders = false

and test the value is properly propagated to the timer component (which is available in the core it)

ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Aug 12, 2019
@ppalaga
Copy link
Contributor Author

ppalaga commented Aug 12, 2019

you can test it by setting:

camel.component.timer.resolve-property-placeholders = false

Thanks for the tip! Did exactly that.

ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Aug 12, 2019
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants