-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Debugger]Avoid need to modify pom.xml to support DataSonnet language #646
Comments
Yeah we should actually go the other way. That languages shown in that "list" is only languages that are available in the running Camel application. The intention is not that you can run any languages "as you wish" but use the languages that your Camel application are using. |
I like this idea, but is there any way in the plugin or in Camel to obtain a list of all languages in the classpath? |
We can see from the JARs on the classpath which ones are langauges and via the camel-catalog find out their names. An alternative is via JMX but then its "only languages that are active in use", eg you may have camel-datasonnet on classpath but it has not been in use yet, then its not registered in camel contexxt. |
Ah, the resolving the new language is taken care of in the |
Yeah I am adding JMX operations to the CamelContextMBean |
currently to evaluate expressions using DataSonnet in debugger, you need to add to the pom.xml:
it is modifying the user project. it would be nice if these dependencies can be injected automatically when needed
The text was updated successfully, but these errors were encountered: