Guillaume,
I think you mean deploy *a* SU on each BC ?
What should be the format of these SUs ?
In my case a helloworld SU contains only two files : a bpel file and a
wsdl file...
My understanding is if I deploy a SU on a component, this component will
say to the NMR that it now offers this service ? Is that OK ?
If yes I don't understand how I can tell in a standard way to a BC that
my SE is offering a new service.
Can you tell me what I should put into my SU I want to deploy in JMS BC
for example ?
Thanks
Charles
Guillaume Nodet wrote:
Hi Charles !
We have already thought about something related to that.
In the JBI way, you should deploy on SU on each BC you want.
You can deploy them inside the same SA that contains your SU for
your BPEL engine.
To achieve this using the lightweight components, you need to
install the servicemix-lwcontainer, on which you can deploy SU
that are servicemix.xml files (just replacing the <sm:container /> tag
with a <sm:serviceunit /> tag.
The loanbroker and soap-binding samples of the 3.0 distribution contains
SUs using the servicemix-lwcontainer. You should look at them.
Cheers,
Guillaume Nodet
Charles Souillard wrote:
Hi all,
I want to know how I can make a service available to all SM
components in a standard way :
I have developed an dinstalled a SE
I have deployed a SA containing two SU. Each one offers a service
To test them, I have started SM with a servicemix.xml file which
declares a new component (hellocomponent).
It is a copy paste from the servicemix.xml of the bpel example.
The JMSClient sends a message to the topic on which hellocomponent is
waiting on.
Then the message is well given to my SE which makes the call...
My question is how can I do that without the servicemix.xml file and
is it possible to make my service available to all BCs installed in
servicemix ?
This functionnality will allow users to contact my app in any
transport way they want.
Thanks
Charles
