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

CamelBlueprintELResolver not detected #18

Open
wiax opened this issue Jan 27, 2015 · 3 comments
Open

CamelBlueprintELResolver not detected #18

wiax opened this issue Jan 27, 2015 · 3 comments

Comments

@wiax
Copy link

wiax commented Jan 27, 2015

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...

@meyerdan
Copy link
Contributor

Form your question I gather that you are using an OsgiProcessApplication?

@wiax
Copy link
Author

wiax commented Jan 27, 2015

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 ?

@rbraeunlich
Copy link
Contributor

Could you show us (part of) your context.xml?

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

3 participants