You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2011/04/26 11:18:03 UTC
[jira] [Created] (CAMEL-3901) Create a separate component for camel
transport for cxf
Create a separate component for camel transport for cxf
-------------------------------------------------------
Key: CAMEL-3901
URL: https://issues.apache.org/jira/browse/CAMEL-3901
Project: Camel
Issue Type: Improvement
Components: camel-cxf
Affects Versions: 2.7.1
Reporter: Christian Schneider
Assignee: Christian Schneider
Fix For: 2.8.0
The camel-cxf component curently contains too many unrelated functions. It contains:
- camel transport for cxf
- cxf component
- cxfbean component
- cxfrs componet
- converters
So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
Some advantages are:
- The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
- The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
- We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
I would be very interested about opinions from other developers about the split.
Christian
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (CAMEL-3901) Create a separate
component for camel transport for cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025578#comment-13025578 ]
Willem Jiang edited comment on CAMEL-3901 at 4/27/11 3:06 AM:
--------------------------------------------------------------
+1 for pulling the camel transport for CXF out of camel-cxf component.
It will help camel-cxf supports the CXF 2.3.x and CXF 2.4.x better.
I think it should be OK if camel-cxf module had no dependency of camel transport, as camel-cxf should not touch the transport part directly.
was (Author: njiang):
+1 for pulling the camel transport for CXF out of camel-cxf component.
I think it should be OK if camel-cxf module had no dependency of camel transport, as camel-cxf should not touch the transport part directly.
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-3901.
---------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.9.0)
2.8.0
Assignee: Willem Jiang (was: Daniel Kulp)
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Willem Jiang
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-3901) Create a separate component for camel
transport for cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CAMEL-3901:
---------------------------------------
Attachment: camel-3901-camel transport-for-cxf.png
Diagram showing the classes in camel transport for cxf
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027620#comment-13027620 ]
Daniel Kulp commented on CAMEL-3901:
------------------------------------
Would anyone object to me adding myself as a "Contributor" to the project in JIRA so I can assign JIRA's to myself?
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025578#comment-13025578 ]
Willem Jiang commented on CAMEL-3901:
-------------------------------------
+1 for pulling the camel transport for CXF out of camel-cxf component.
I think it should be OK if camel-cxf module had no dependency of camel transport, as camel-cxf should not touch the transport part directly.
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027594#comment-13027594 ]
Christian Schneider commented on CAMEL-3901:
--------------------------------------------
Dan has shown interest to implement this. It will take some time though as he can only start in some weeks.
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025145#comment-13025145 ]
Claus Ibsen commented on CAMEL-3901:
------------------------------------
Great move Christian. I would love CXF and Camel integration to be lighter.
And more ala carte. Such as if you only need REST etc.
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-3901) Create a separate component for
camel transport for cxf
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CAMEL-3901:
----------------------------------
Assignee: Daniel Kulp (was: Christian Schneider)
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Daniel Kulp
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-3901) Create a separate component for camel
transport for cxf
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3901:
-------------------------------
Fix Version/s: (was: 2.8.0)
2.9.0
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Daniel Kulp
> Fix For: 2.9.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-3901) Create a separate component for camel
transport for cxf
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated CAMEL-3901:
---------------------------------------
Attachment: camel-3901-1.patch
Simply removed everything that is not related to camel transport for cxf. The code is only about 870 lines
> Create a separate component for camel transport for cxf
> -------------------------------------------------------
>
> Key: CAMEL-3901
> URL: https://issues.apache.org/jira/browse/CAMEL-3901
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 2.7.1
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 2.8.0
>
> Attachments: camel-3901-1.patch, camel-3901-camel transport-for-cxf.png
>
>
> The camel-cxf component curently contains too many unrelated functions. It contains:
> - camel transport for cxf
> - cxf component
> - cxfbean component
> - cxfrs componet
> - converters
> So this causes the code of the component to depend on each other and suck in much too many dependencies. Besides this there are some package dependency cycles in the code which could easily be solved.
> A first step is to separate the camel transport for cxf from the rest of the code. It is independent of all other code and can be pulled into a new component.
> Some advantages are:
> - The camel transport for cxf needs very few dependencies so it is a vey light weight aproach to combine cxf and camel
> - The new component nicely shows how to bridge between cxd and camel without the overhead of the other components
> - We can let the camel-cxf component depdend on the camel transport for cxf so for people using maven no changes are needed
> I will attach a patch where I simply deleted anything that is not relevant for camel transport for cxf from the camel-cxf project. This is of course not yet the solution but it shows how small the new component will be and is a good start for doing the split.
> I would be very interested about opinions from other developers about the split.
> Christian
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira