On 19 October 2010 13:59, Schneider Christian <[email protected]> wrote: > Hi James, > > it is not absolutely necessary to split the jar into three jars. More > important is to have rules that say that a component developer should only > depdend on the API part and to check that the internal dependencies do not > have cycles between the three logical modules. The only disadvantage of not > breaking up camel core into three modules is that maven will not help you in > avoiding cycles which would be the case with separate modules. As the rules > can be checked with tools like structure 101 this is not too bad though. > > I don´t think the cyclic depdencies are only a "metric". They are a real > problem when the code grows as you can not understand or change anything > isolated. To have three clearly defined parts in camel core that should not > have cycles between them is quite reasonable imho. > > Especially I think the builders should be separated as they are not needed at > runtime.
I don't follow this comment. When would the builders and DSL be used other than at runtime? Every use case I've seen of the builders and DSLs is for runtime stuff; defining routes at runtime; often using runtime dependency injection. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
