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
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 ManagedBacklogDebugger, it calls camelContext.resolveLanguage() before evaluating the expression.
So by "via JMX" did you mean there's an existing functionality that I can use or that we need to implement a new call?
Perhaps add something like getResolvedLanguages() to the Camel context?
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: