camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CAMEL-1261) camel-spring - method call language can not be used with split
Date Thu, 15 Jan 2009 14:43:04 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48729#action_48729
] 

jstrachan edited comment on CAMEL-1261 at 1/15/09 6:42 AM:
----------------------------------------------------------------

kinda conflused by this - as SplitterType is an ExpressionNode (just like filter, when) so
it should allow expressions as children?

{code}
<split>
 <method bean="echoService" method="splitWords"/>
</split>
{code}

this works for me in IntelliJ. Indeed there's a test case splitterWithCustomThreadPoolExecutor.xml
in camel-spring

      was (Author: jstrachan):
    kinda conflused by this - as SplitterType is an ExpressionNode (just like filter, when)
so it should allow expressions as children?

{code>
<split>
 <method bean="echoService" method="splitWords"/>
</split>
{code}

this works for me in IntelliJ. Indeed there's a test case splitterWithCustomThreadPoolExecutor.xml
in camel-spring
  
> camel-spring - method call language can not be used with split
> --------------------------------------------------------------
>
>                 Key: CAMEL-1261
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1261
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core, camel-spring
>    Affects Versions: 1.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.1, 2.0.0
>
>
> Using a method call for the split expression is not possible in Spring DSL. It wants
to resolve the language.
> As we dont have all the expression builder helper in Spring XML its a bit harder to do
routing. But I want to use a bean for the splitting. End users should always have the true
power of java, regardless.
> {code}
>             <split>
>                 <expression>
>                     <method bean="echoService" method="splitWords"/>
>                 </expression>
>                 <to uri="bean:echoService?method=hello"/>
>                 <to uri="stream:out"/>
>             </split>
> {code}
> And gives this exception:
> {code}
> 2009-01-15 14:15:18,831 [ing.Main.main()] ERROR MainSupport                    - Failed:
org.apache.camel.NoSuchLanguageException: No language could be found for: null
> org.apache.camel.NoSuchLanguageException: No language could be found for: null
>         at org.apache.camel.impl.DefaultLanguageResolver.noSpecificLanguageFound(DefaultLanguageResolver.java:72)
>         at org.apache.camel.impl.DefaultLanguageResolver.resolveLanguage(DefaultLanguageResolver.java:52)
>         at org.apache.camel.impl.DefaultCamelContext.resolveLanguage(DefaultCamelContext.java:430)
>         at org.apache.camel.model.language.ExpressionType.createExpression(ExpressionType.java:158)
>         at org.apache.camel.model.SplitterType.createProcessor(SplitterType.java:86)
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message