A binding component should only include protocol normalization operations. So you're right when you say you will need two components: the first one is servicemix-http which will handle HTTP (+SOAP) protocol. The second one needs to invoke your shell script, but you can take a look at our POJOs support using servicemix-jsr181, servicemix-bean or servicemix-lwcontainer. You could also write a full service engine which role would be to launch shell scripts (i think it's more a SE than a BC).
On 3/12/07, Owen Thomas <[EMAIL PROTECTED]> wrote:
Hello again. Hoping the extra words in the heading clarify. I think my question might be too general to get help on. Anyway, I would appreciate the help that anyone could offer. I'm approaching a time when I finish looking at the theory of JBI, and concentrate solely on code. I want to cut the code that gives me my first realisation of a web service, and just looking for some sanguine words of encouragement. I would welcome more cautious words of foreboding; words that might stop me from a month or two of frustration. Thanks... here goes, Owen. -----Original Message----- From: Owen Thomas [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 3:10 PM To: [email protected] Subject: Exposing JBI as web service. Hello. I would like some confirmation that what I'm thinking is right, or if it isn't, some clarification would be welcome. Exposing the invocation of a shell script as a web service, I will put a JBI implementation on a JVM which is hosted on the same machine as the shell script resides. I will use ServiceMix as the JBI container, and will have two binding components: one that executes the shell script (it look as if I will have to write this), and the other will use the servicemix-http binding component so the first binding component can be called as a web service. Does all of this sound right? Is there anyone who might want to question what I'm doing? Thanks for your replies, Owen.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
