You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Willem Jiang <wi...@gmail.com> on 2009/04/29 12:02:58 UTC
[DISCUSS] Break camel-core into camel-api and camel-core
Hi riders,
I'm thinking to do some refactoring of Camel test support to let
camel-core depends on camel-test.
In this way we just have one copy of TestSupport and CamelTestSupport.
Because camel-test has the dependence of CamelContext ,
ProducerTemplate, Service, RouteBuilder, etc, I'd like to break current
camel-core module into camel-api and camel-core, and the camel-test will
depends on the camel-api only. Then we can share the camel-test code
around all the camel-components and camel-core.
Since CamelTestSupport has the dependency of the CamelBeanPostProcessor
, we could put it into the camel-spring module.
Any thought?
Willem
Re: [DISCUSS] Break camel-core into camel-api and camel-core
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Apr 30, 2009 at 11:38 AM, Willem Jiang <wi...@gmail.com> wrote:
> Hi Claus,
>
> Here is another benefit of spreate the camel-api with camel-core. We
> could drop a clean line between the user API and internal API.
None of the others do it that I am aware of. spring-core.jar does
contain impl and API in same .jar.
I was wondering if the OSGi export packages should reflect the public
API of Camel,
so we can leverage that to expose the public API.
I would really dislike to work with two maven projects to maintain and
work on Camel.
>
> I can live with sync the camel-test with camel-core by the copying script.
Yeah its after all only 1 or 2 classes in camel-test.
>
> Thanks,
>
> Willem
>
> Claus Ibsen wrote:
>> On Wed, Apr 29, 2009 at 12:02 PM, Willem Jiang <wi...@gmail.com> wrote:
>>> Hi riders,
>>>
>>> I'm thinking to do some refactoring of Camel test support to let
>>> camel-core depends on camel-test.
>>>
>>> In this way we just have one copy of TestSupport and CamelTestSupport.
>>> Because camel-test has the dependence of CamelContext ,
>>> ProducerTemplate, Service, RouteBuilder, etc, I'd like to break current
>>> camel-core module into camel-api and camel-core, and the camel-test will
>>> depends on the camel-api only. Then we can share the camel-test code
>>> around all the camel-components and camel-core.
>>>
>>> Since CamelTestSupport has the dependency of the CamelBeanPostProcessor
>>> , we could put it into the camel-spring module.
>>>
>>> Any thought?
>> If the only purpose is to keep camel-test in sync with camel-core then
>> I am not keen on this.
>>
>> We have many interfaces and much more in camel-core that constitutes
>> the API. We have the implementation in component, impl and processor.
>>
>> And working on both in a single project is much easier with SVN and
>> your editor such as Eclipse or IDEA.
>>
>> In the works for Camel 2.0 we have changed or refactored the code
>> numerous times and I doubt it would have been so easy if the code was
>> split.
>>
>> Isnt it possible to keep camel-test in sync by some copy script that
>> can copy the src from camel-core to camel-test so its automatic
>> updated.
>>
>>
>>
>>
>>> Willem
>>>
>>
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
Re: [DISCUSS] Break camel-core into camel-api and camel-core
Posted by Willem Jiang <wi...@gmail.com>.
Hi Claus,
Here is another benefit of spreate the camel-api with camel-core. We
could drop a clean line between the user API and internal API.
I can live with sync the camel-test with camel-core by the copying script.
Thanks,
Willem
Claus Ibsen wrote:
> On Wed, Apr 29, 2009 at 12:02 PM, Willem Jiang <wi...@gmail.com> wrote:
>> Hi riders,
>>
>> I'm thinking to do some refactoring of Camel test support to let
>> camel-core depends on camel-test.
>>
>> In this way we just have one copy of TestSupport and CamelTestSupport.
>> Because camel-test has the dependence of CamelContext ,
>> ProducerTemplate, Service, RouteBuilder, etc, I'd like to break current
>> camel-core module into camel-api and camel-core, and the camel-test will
>> depends on the camel-api only. Then we can share the camel-test code
>> around all the camel-components and camel-core.
>>
>> Since CamelTestSupport has the dependency of the CamelBeanPostProcessor
>> , we could put it into the camel-spring module.
>>
>> Any thought?
> If the only purpose is to keep camel-test in sync with camel-core then
> I am not keen on this.
>
> We have many interfaces and much more in camel-core that constitutes
> the API. We have the implementation in component, impl and processor.
>
> And working on both in a single project is much easier with SVN and
> your editor such as Eclipse or IDEA.
>
> In the works for Camel 2.0 we have changed or refactored the code
> numerous times and I doubt it would have been so easy if the code was
> split.
>
> Isnt it possible to keep camel-test in sync by some copy script that
> can copy the src from camel-core to camel-test so its automatic
> updated.
>
>
>
>
>> Willem
>>
>
>
>
Re: [DISCUSS] Break camel-core into camel-api and camel-core
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Apr 29, 2009 at 12:02 PM, Willem Jiang <wi...@gmail.com> wrote:
> Hi riders,
>
> I'm thinking to do some refactoring of Camel test support to let
> camel-core depends on camel-test.
>
> In this way we just have one copy of TestSupport and CamelTestSupport.
> Because camel-test has the dependence of CamelContext ,
> ProducerTemplate, Service, RouteBuilder, etc, I'd like to break current
> camel-core module into camel-api and camel-core, and the camel-test will
> depends on the camel-api only. Then we can share the camel-test code
> around all the camel-components and camel-core.
>
> Since CamelTestSupport has the dependency of the CamelBeanPostProcessor
> , we could put it into the camel-spring module.
>
> Any thought?
If the only purpose is to keep camel-test in sync with camel-core then
I am not keen on this.
We have many interfaces and much more in camel-core that constitutes
the API. We have the implementation in component, impl and processor.
And working on both in a single project is much easier with SVN and
your editor such as Eclipse or IDEA.
In the works for Camel 2.0 we have changed or refactored the code
numerous times and I doubt it would have been so easy if the code was
split.
Isnt it possible to keep camel-test in sync by some copy script that
can copy the src from camel-core to camel-test so its automatic
updated.
>
> Willem
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration