You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Owen Thomas <ot...@wcg.net.au> on 2007/03/12 06:36:49 UTC
RE: Exposing JBI [implentation on an internal system host] as web service.
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:othomas@wcg.net.au]
Sent: Monday, March 12, 2007 3:10 PM
To: servicemix-users@geronimo.apache.org
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.
Re: Exposing JBI [implentation on an internal system host] as web service.
Posted by Bruce Snyder <br...@gmail.com>.
On 3/12/07, Owen Thomas <ot...@wcg.net.au> wrote:
> Hi Giullaume
>
> Thanks to you and Bruce for the tip. I think that it would be great to
> keep away from writing a component because I looked at what classes and
> interfaces a BC had to extend and implement, and it aint pretty. Your
> advice is welcome indeed.
>
> What is the difference between a BC and SE? Is this difference manifest
> in the API so that knowing which one to develop is obvious?
The differences between the two are certainly subtle. Below are
explanations of each one:
* Service engines (SEs) are engines that are deployed to the JBI
container and communicate only using normalized messages.
** Example: Consider deploying a BPEL engine to the JBI container -
this is deployed as a SE because it handles business process script
execution via the BPEL engine.
* Binding components (BCs) are bindings to services external to the
JBI container and use a remote protocol for communication with that
service.
** Example: Consider the servicemix-http BC which is used to
communicate with services external to the JBI container via the HTTP
protocol.
Does that help?
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
RE: Exposing JBI [implentation on an internal system host] as web service.
Posted by Owen Thomas <ot...@wcg.net.au>.
Hi Giullaume
Thanks to you and Bruce for the tip. I think that it would be great to
keep away from writing a component because I looked at what classes and
interfaces a BC had to extend and implement, and it aint pretty. Your
advice is welcome indeed.
What is the difference between a BC and SE? Is this difference manifest
in the API so that knowing which one to develop is obvious?
Owen.
-----Original Message-----
From: Guillaume Nodet [mailto:gnodet@gmail.com]
Sent: Monday, March 12, 2007 6:48 PM
To: servicemix-users@geronimo.apache.org
Subject: Re: Exposing JBI [implentation on an internal system host] as
web service.
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 <ot...@wcg.net.au> 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:othomas@wcg.net.au]
> Sent: Monday, March 12, 2007 3:10 PM
> To: servicemix-users@geronimo.apache.org
> 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/
Re: Exposing JBI [implentation on an internal system host] as web service.
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <ot...@wcg.net.au> 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:othomas@wcg.net.au]
> Sent: Monday, March 12, 2007 3:10 PM
> To: servicemix-users@geronimo.apache.org
> 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/