Hi, 1) once the components where stored under "deployables/...". This changed to ease the sharing of the components between ServiceMix 3 and 4.
We do not add components to the old position any longer. If you don't plan to contribute your new component to the ServiceMix project it isn't even needed that you code directly in ServiceMix. You can also develop BC's /SE's independently from the ServiceMix sources. I suggest to read the tutorials section of our project webpage, especially the helloworld-bc/se stuff. It is not up2date and may not work at all but it gives you an explanation how to create a binding component. 2) Doing a component is not all the work what should be done. You also need to do a service-unit for your new component and deploy this inside a SA into the bus. This will cause the servicemix to create an endpoint for your new component. I would suggest here to have a short look at the JBI spec as it seems you are missing some dependencies here. If you got further questions, feel free to ask here. Regards Lars Am Mittwoch 01 Oktober 2008 23:32:05 schrieb rinku24: > I am newbee to servicemix architecture. I have to implement SMPP binding > component. > > Initially I implemented smppbc under > src/deployables/bindingcomponents/servicemix-smpp. It deploys find and I > see in the log that component has started from SMPPComponent class but it > never invoked SMPPEndpoint class where it binds to SMSC and waits for > incoming SMS. > > Than I created a SMPPPoller and SMPPSender classes under > src/common/servicemix-components/smpp directory and I was able to start > servicemix using servicemix.xml for SMPPPoller class whose destination > service is SMPPSender and working fine. > > 1. What is the different between deployable binding component versus > servicemix-component? > 2. When Endpoint class is invoked in deployable binding components? > > I would really appreciate your help.
