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 (JIRA)" <ji...@apache.org> on 2009/06/08 07:02:36 UTC

[jira] Commented: (CAMEL-1677) Remove dependency cycles between model and sub packages

    [ https://issues.apache.org/activemq/browse/CAMEL-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52111#action_52111 ] 

Willem Jiang commented on CAMEL-1677:
-------------------------------------

@Christian , 

You patch doesn't include the change of CamelNamespaceHandler of the camel-spring module.
Don't worry, I will take care of it :)

Willem


> Remove dependency cycles between model and sub packages
> -------------------------------------------------------
>
>                 Key: CAMEL-1677
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1677
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0-M1
>            Reporter: Christian Schneider
>            Assignee: Willem Jiang
>             Fix For: 2.0-M2
>
>         Attachments: camel-core.patch, model-before.png, model_after.png
>
>
> Currently there is a dependency cycle between model and model.loadbalancer and between model and model.dataformat. The reason in both cases that the base classes DataFormatDefinition and LoadBalancerDefinition are in the subpackages but are referenced from model. 
> I think the goal should be that model does not reference the subpackages.
> The easy solution is to move the two classes above to model. After the move the cycles are gone.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.