[
https://issues.apache.org/activemq/browse/SM-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45183#action_45183
]
Gert Vanthienen commented on SM-1455:
-------------------------------------
You cannot move the classes out of the container, but it should be possible to
add a package with ServiceMix-specific extensions to the JBI 1.0 API
({{org.apache.servicemix.jbi.api}}) to servicemix-utils containing these two
interfaces:
- {{Container}} represents a ServiceMix JBI Container -- it's up to SMX3 and
SMX4 to implement it, the components can use the interface if they need access
to the container instead of using the {{JBIContainer}} class
- {{MessageExchangeListener}} that is the same one as we use now -- we keep the
old one around for backward compatibility but deprecate it and make it extend
the new one
The {{ComponentMBeanImpl}} is only use by HTTPManagedServlet apparently for
getting access to the {{Component}}, but we don't need that if our new
{{Container}} interface provides convenient access to the {{Component}}. Wdyt?
> Reduce dependency cycle between ServiceMix 3 container and the components
> --------------------------------------------------------------------------
>
> Key: SM-1455
> URL: https://issues.apache.org/activemq/browse/SM-1455
> Project: ServiceMix
> Issue Type: Bug
> Affects Versions: 3.3
> Reporter: Gert Vanthienen
> Priority: Critical
> Fix For: 3.3
>
>
> Currently, building the components depends on a successful build of the
> container and vica versa.
> We should reduce this dependency cycle as it is impossible to do a release
> this way.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
