Just a heads up to explain what i'm about to do in the smx3 components.
My goal is to be able to get rid of the JBI packaging in smx4, which
means deploying plain OSGi bundles instead of the JBI components, and
also being able to deploy servicemix endpoints via the OSGi registry
instead of using service units.
This means:
* transform some of smx3 jars into OSGi bundle (currently
servicemix-services, servicemix-common the other dependencies)
* transform components into OSGi bundles and add a spring xml file
to create and register the component in the OSGi registry
* enhance servicemix-common to be able to create an OSGi service
listener that will wire endpoints in the OSGi registry to the
component and activate them
The goal is to be able to use a single spring xml file to wire
everything, from camel routes, to cxf and smx endpoints.
To activate an endpoint, you would use something like:
<beans>
<eip:wire-tap id="endpoint" service="xxx" endpoint="xxx">
...
</eip:wire-tap>
<osgi:service ref="endpoint">
<osgi:interfaces>
<value>org.apache.servicemix.eip.EIPEndpoint</value>
</osgi:interfaces>
</osgi:service>
</beans>
Expect a few commits in the 3.3 branch soon about that.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
