Hi Hold your horses ... Camels.
It can get too confusing and complex syntax if you can inline any other kind of languages in the simple language. Syntax parsers and whatnot cannot validate and parse the other languages syntax etc. The name of the language is simple, so lets try to keep it that way. Also with xpath there is the namepsace problem, and as well to define a result type etc. On Fri, Sep 20, 2013 at 11:39 PM, Christian Posta <[email protected]> wrote: > yah i like that. can you open a jira? > > > On Fri, Sep 20, 2013 at 9:36 AM, Dale King <[email protected]> wrote: > >> Perhaps adding language prefixes so that things like ${xpath:...} or >> ${ognl:...} and similar would work. >> >> >> On Fri, Sep 20, 2013 at 11:17 AM, bonnahu <[email protected]> wrote: >> >> > Hi Christian, >> > I think it would be useful if we have such "composite" expression. What >> do >> > you think? >> > >> > >> > >> > -- >> > View this message in context: >> > >> http://camel.465427.n5.nabble.com/Is-it-possible-to-include-XPath-expression-in-simple-expression-tp5739830p5739882.html >> > Sent from the Camel - Users mailing list archive at Nabble.com. >> > >> >> >> >> -- >> Dale King >> > > > > -- > *Christian Posta* > http://www.christianposta.com/blog > twitter: @christianposta -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
