On Fri, Sep 2, 2011 at 6:41 AM, James Strachan <ja...@fusesource.com> wrote: > I'm also not sure how much smaller we can really get camel-core; since > out of the box you'd assume camel can work with JMX, beans, files & > implement the patterns and have the model in there. Shaving off > 20-100k doesn't seem that big a deal IMHO; the bean / file stuff isn't > that big.
I actually use Camel without using JMX, beans or files. But I'm maybe not a typical user. Not sure about the use of the term "out of the box" here. Right now the entire Camel package is available as a single download, including all components. Assuming one unpacks the whole thing at once, any component without external dependencies should work "out of the box", and it shouldn't matter whether it's part of the core or not. "Out of the box" should only be an issue when someone has a particular need, such as a desire to shave off every byte one can. That's when one starts selectively importing jars, unpacking and rebuilding manifests and other fun stuff. Otherwise it shouldn't matter if the core was one piece or five, as long as all pieces were there. FWIW I agree that cleaving the core and restructuring the API is better earmarked for 3.0. Major releases are a good context for major changes. Perhaps the majority of users will adopt 3.0 before the release of 2.9.15. Don
