-
Bug
-
Resolution: Done
-
Major
-
7.2.2
-
Fuse Tooling Version: 7.2.2.v20140908-1338-H92-Final
JBoss Developer Studio Version: 7.1.1.GA v20140314-2145-B688
Java HotSpot(TM) 64-Bit Server VM 1.7.0_60 on Fedora 20java.version=1.7.0_60
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Oracle Corporation
java.vm.specification.version=1.7
java.vm.vendor=Oracle Corporation
java.vm.version=24.60-b09os.arch=amd64
os.name=Linux
os.version=3.17.7-200.fc20.x86_64Fuse Tooling Version: 7.2.2.v20140908-1338-H92-Final JBoss Developer Studio Version: 7.1.1.GA v20140314-2145-B688 Java HotSpot(TM) 64-Bit Server VM 1.7.0_60 on Fedora 20 java.version=1.7.0_60 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Oracle Corporation java.vm.specification.version=1.7 java.vm.vendor=Oracle Corporation java.vm.version=24.60-b09 os.arch=amd64 os.name=Linux os.version=3.17.7-200.fc20.x86_64
-
Sprint 2
-
There is no way to define a grouped split like below using the graphical editor because the token doesn't support group property. You can do that by editing the xml code, but grouping is not reflected on the tokenizer properties tab.
<route> <from uri="file:inbox"/> <split streaming="true"> <tokenize token="\n" group="1000"/> <to uri="activemq:queue:order"/> </split> </route
In fact, the way to define it directly on source code looks as ugly as this...
<tokenize token="\n" group="100">"\n"</tokenize>
Where the element content ...>"\n"<... cheats the graphical editor, while the <tokenize token="\n" group="100"> does the real job...
