-
Notifications
You must be signed in to change notification settings - Fork 345
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
Saga example #1097
Comments
We should leverage the service loader mechanism available in Camel for such kind of things, I was expecting the service to be recognized automatically. Also properties should be recognized by Camel main in order to be used in Camel K. |
Thanks @nicolaferraro , so the feature has not been supported in the camel-k currently ? |
I meant that if we fix it in Camel, we can avoid adding boilerplate in Camel K, but it should be supported. You can bind a LRASagaService using bean binding also in Camel K. |
sure, I get it. |
@nicolaferraro can you review #1109 please ? |
I just add the LRASagaService in the router configuration. |
@zhfeng @apache/camel-committers should we add a saga customizer in camel-k-runtime ? or will this issue be fixed on camel side ? |
@lburgazzoli I think it could be better to be fixed on the camel side if possible. |
@zhfeng o can you open an issue on camel side and close this one ? |
yeah, I will |
I raise CAMEL-15164 for services recognize automatically and since the Saga examples have been merged. So I close this issue now and if the CAMEL-15164 is resolved in the future camel releases, I would like to investigate to see how we can leverage it to improve this example. |
I'm working on the camel-saga-quickstart to run with the camel-k.
At first, I added the detection to check
"*\.saga\(\).*"
and add camel-lra dependency. It works fine and I get the example running but throws exceptionIt looks like there is no CamelSagaService. I checked the camel-lra-starter which invokes the following
So I wonder how we can add a CamelSagaService in camel-k similarly ?
The text was updated successfully, but these errors were encountered: