i was scrubbing this page when i saw two endpoint options that both appear to limit the capacity of the SEDA queue - size, and queueSize [1].
if i'm reading the trunk [2] correctly, i believe *size* is the queue capacity, whereas queueSize is the actual capacity utilization and is not actually a (configurable) endpoint option. is it okay for me to remove the queueSize entry from the options list? or is this something that changed from prior versions and deserves a notation to that effect? [1]: https://cwiki.apache.org/confluence/pages/diffpages.action?originalId=27838166&pageId=27844297 [2]: http://svn.apache.org/viewvc/camel/trunk/camel-core/src/main/java/org/apache/camel/component/seda/SedaEndpoint.java?view=markup ~ Reuben On Wed, Apr 18, 2012 at 4:58 AM, <conflue...@apache.org> wrote: > SEDA <https://cwiki.apache.org/confluence/display/CAMEL/SEDA> Page * > edited* by Claus > Ibsen<https://cwiki.apache.org/confluence/display/%7Edavsclaus> > Changes (1) > ... > | {{blockWhenFull}} | {{false}} | *Camel 2.9:* Whether to block the > current thread when sending a message to a SEDA endpoint, and the SEDA > queue is full (capacity hit). By default an exception will be thrown > stating the queue is full. By setting this option to {{true}} the caller > thread will instead block and wait until the message can be delivered to > the SEDA queue. | > | {{queueSize}} | | *Camel 2.9:* The maximum size (capacity of the number > of messages it can hold) of the SEDA queue. | > | {{pollTimeout}} | {{1000}} | *Camel 2.10:* Consumer only. The timeout > used when polling. When a timeout occurs then the consumer can check > whether its allowed to continue to run. Setting a lower value allows the > consumer to react faster upon shutting down. | >
