[jira] [Updated] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-11 Thread Charles Moulliard (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Charles Moulliard updated CAMEL-10136:
--
Affects Version/s: (was: 2.15.3)

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (CAMEL-10136) Missing Group attribute for Tokenize DSL added to the Body Expression

2016-07-11 Thread Charles Moulliard (JIRA) 

 [ 
https://issues.apache.org/jira/browse/CAMEL-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Charles Moulliard updated CAMEL-10136:
--
Summary: Missing Group attribute for Tokenize DSL added to the Body 
Expression  (was: Missing Group attribute for Token DSL)

> Missing Group attribute for Tokenize DSL added to the Body Expression
> -
>
> Key: CAMEL-10136
> URL: https://issues.apache.org/jira/browse/CAMEL-10136
> Project: Camel
>  Issue Type: Bug
>Affects Versions: 2.15.3
>Reporter: Charles Moulliard
>
> The option group ("",".tokenize("\n", 
> 1000)") doesn't exist when we use the Tokenize DSL after a body expression
> {code}
> .split(body(String.class).tokenize("\n")).streaming()
> {code}
> but only when we create append the .tokenize() DSL to the splitter
> {code}
> .split().tokenize("\n",3).streaming()
> {code}
> Question : Is it the expected behaviour or something missing ?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)