Hi Lou,
1. When developing components using servicemix-bean is there a distinction
between binding component and service engine?
I think that you talk on developing service unit. I guess that you have
coded a service unit (defining a servicemix-bean endpoint). Your service
unit uses servicemix-bean component and you have defined the
configuration using a xbean.xml. Correct ?
If you have defined a service unit, it extends the component behavior
(as it's a kind of specialization of the component). The endpoint
behavior depends of the component and your configuration in the
xbean.xml. servicemix-bean component works only in provider mode. As
servicemix-bean is a service engine, it acts as provider (consumer
doesn't make sense for a service engine).
2. My component would typically be considered a binding component (I
think?). Is this accurate even though it is developed as bean component?
Site documents servicemix-bean as a service engine component.
The purpose of a binding component is to communicate for external system
(FTP, mail, JMS, etc). I don't see why you need to create your own
component. You can define a "chain" of component/endpoint and route
using JBI (target service and endpoint).
Could we have some example of your binding component ?
Regards
JB
--
Jean-Baptiste Onofré (Nanthrax)
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net
[email protected]
PGP : 17D4F086
