Hi, ok lets see if I understand your use case right. You have a WS that listens for messages, when it gets a message it forwards it to a queue. To the queue are some listeners attached, that read messages and then take them out and forward them to some other service.
So first I would take a look at the jms example and find out how it works. Look how jms consumer and jms producers work. Then the next setup would be to decide if you need a topic or a queue for your use case. Then write the Binding Components (email, sms, etc) and attach them to the NMR. You should take a look at the jbi spec for that. It helped me a lot to understand how BCs work and also look at how the standard components in SM are written. So now you can wire every thing together with a servicemix.xml file. To be honest it takes some time to understand the concept and get everything working. At least when you are totally new to xbeans, queues, SM and AMQ like me. I have left out how to integrate your WS into SM. That the point I am working at in the moment and try to understand how to do it. I hope this helps you a bit. cya mike -----Ursprüngliche Nachricht----- Von: mqaiserm [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 30. März 2006 16:54 An: [email protected] Betreff: Re: https Hi Mike, Looks like you have good exp working with servicemix. wondering that if you can help me for startup. I am new to servicemix and want to integrate in our system. The use case is A Webservice is listening for messages , asap messages come, register them with one designated Queue, and there are some listener attached to queues , after receiving any message they delived message to proper desitination (db , email, sms text etc). Any idea from where I should start ? -- View this message in context: http://www.nabble.com/servicemix-default-port-t1357054.html#a3671580 Sent from the ServiceMix - User forum at Nabble.com. This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message.
