You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to use the Camel integration inside Camunda with Blueprint. For more information, I create a ProcessApplication with the annotation and I declare the process engine via processes.xml.
And for sure, I create the specific EL resolver for Camel:
It seems that the ProcessApplicationElResolverDelegate doesn't find the ProcessApplicationReference. Context.getCurrentProcessApplication() returns null.
Any idea? Missing configuration?
I see that the ProcessApplicationReference is expected to be stored in a ThreadLocal, but for each request it's a different thread...
The text was updated successfully, but these errors were encountered:
Yes I created a class extending OsgiProcessApplication.
I have the following error: "Unknown property used in expression: #{camel.sendTo('direct:syncService')}. Cause: Cannot resolve identifier 'camel'"
It's probably due to the fact that the CamelBlueprintELResolver is not detected. But I declared the CamelBlueprintELResolver bean.
I think the CamelBlueprintELResolver is exposed by the class OsgiProcessApplication.
Can you tell why I have this error ?
Do I forget to configure something ?
How is the CamelBlueprintELResolver detected ? And used by ? ProcessApplicationElResolverDelegate ?
Hi,
I try to use the Camel integration inside Camunda with Blueprint. For more information, I create a ProcessApplication with the annotation and I declare the process engine via processes.xml.
And for sure, I create the specific EL resolver for Camel:
It seems that the ProcessApplicationElResolverDelegate doesn't find the ProcessApplicationReference. Context.getCurrentProcessApplication() returns null.
Any idea? Missing configuration?
I see that the ProcessApplicationReference is expected to be stored in a ThreadLocal, but for each request it's a different thread...
The text was updated successfully, but these errors were encountered: