On 21/01/2008, Christian Schneider <[EMAIL PROTECTED]> wrote: > > Thanks for your descriptions of the camel packages. I will prepare a wiki > page to document them. Currently I do not have write access to the wiki. Is > it possible that I could directly work on the wiki?
Definitely! See here on why its not open by default (due to wiki spam). http://activemq.apache.org/camel/how-do-i-edit-the-website.html we just need your username you registered with confluence > In the recent days I have tried to disentangle the spi and camel package. > What I found is that spi and camel can not be brought into a hierarchy in > the current structure as they reference each other too much. > I found a possible solution though. My suggestion is to move all interfaces > from camel to spi and rename the package spi to api. Of course spi and api > could be separated but till now I found no clean way to do this. Am a bit worried renaming the camel package as it'll break everyones code. I wonder if we just move the interfaces from the SPI package into the core camel package? > In any case camel could be based mainly on an interface based api package. > Of course this would be a step to be planned well as it has implications on > almost every component and class in camel. > > I think the camel modules should be described separately. The good thing > about the modules is that there is no danger that camel-core refrences a > module. I have already created a jira issue to factor the remaining > components like the file component to a separate module to emphasize that > the core is independent of them. Cool. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com
