How could using the split pattern avoid memory overload?

[ext2 <xu...@tongtech.com>]

Hi
	I always to do  work , it seems "the split pattern" could resolve,
but will encounter memory overload problem. To illustrate the problem, lets'
take  a example: 
	Often , we need to query records from a database , but the records
matched the condition are too much , and cannot load them to memory at all. 

	Although , using camel's splitter pattern , I could write a bean to
read database ,and  the splitter pattern ask for the bean must read all the
record and return them in a list. But this will cause critical problem.
	So is there any other means  to resolve this problem in camel? 

Thanks for any suggestion

Re: How could using the split pattern avoid memory overload?

[ext2 <xu...@tongtech.com>]

Oh, I am stupid;
The camel's document said clearly, the bean return iterator, and using
stream model could resolve my problem;
-----------------------------------------------------------------------
Does the split-pattern support the bean-express to return a Enumeration
instead of List?

----------------------------------------------------------------------------
Hi
	I always to do  work , it seems "the split pattern" could resolve,
but will encounter memory overload problem. To illustrate the problem, lets'
take  a example: 
	Often , we need to query records from a database , but the records
matched the condition are too much , and cannot load them to memory at all. 

	Although , using camel's splitter pattern , I could write a bean to
read database ,and  the splitter pattern ask for the bean must read all the
record and return them in a list. But this will cause critical problem.
	So is there any other means  to resolve this problem in camel? 

Thanks for any suggestion

Re: How could using the split pattern avoid memory overload?

[ext2 <xu...@tongtech.com>]

Does the split-pattern support the bean-express to return a Enumeration
instead of List?

----------------------------------------------------------------------------
Hi
	I always to do  work , it seems "the split pattern" could resolve,
but will encounter memory overload problem. To illustrate the problem, lets'
take  a example: 
	Often , we need to query records from a database , but the records
matched the condition are too much , and cannot load them to memory at all. 

	Although , using camel's splitter pattern , I could write a bean to
read database ,and  the splitter pattern ask for the bean must read all the
record and return them in a list. But this will cause critical problem.
	So is there any other means  to resolve this problem in camel? 

Thanks for any suggestion