You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by jb...@nanthrax.net on 2009/02/03 14:24:04 UTC
servicemix-exec component
Guys,
In parallel of the discussion "share components between Camel and SMX", I'm going to begin
a servicemix-exec component.
This component will be able to launch command (command and/or arguments can be provided in the NormalizedMessage), get the stdout/stderr stream and send back in the NMR (in a NormalizedMessage).
Basicly, this component can be view :
- as a binding component : if we consider the command outside SMX.
- as a service engine : as the input and output going through the NMR, we can consider the command as a "business" logic and so the component is a service engine.
I would like to have your feedback about this : do you consider this component as a BC or a SE ?
My apologize is the question looks stupid :)
Regards
JB
Re: servicemix-exec component
Posted by jb...@nanthrax.net.
Agree Guillaume.
Thanks for your feedback.
JB
On Tuesday 03 February 2009 - 14:45, Guillaume Nodet wrote:
> I would rather put it in the SE category because it can not really be
> accessed from an external client and does not handle a known protocol.
>
> On Tue, Feb 3, 2009 at 14:24, <jb...@nanthrax.net> wrote:
> > Guys,
> >
> > In parallel of the discussion "share components between Camel and SMX", I'm going to begin
> > a servicemix-exec component.
> >
> > This component will be able to launch command (command and/or arguments can be provided in the NormalizedMessage), get the stdout/stderr stream and send back in the NMR (in a NormalizedMessage).
> >
> > Basicly, this component can be view :
> > - as a binding component : if we consider the command outside SMX.
> > - as a service engine : as the input and output going through the NMR, we can consider the command as a "business" logic and so the component is a service engine.
> >
> > I would like to have your feedback about this : do you consider this component as a BC or a SE ?
> >
> > My apologize is the question looks stupid :)
> >
> > Regards
> > JB
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
Re: servicemix-exec component
Posted by Guillaume Nodet <gn...@gmail.com>.
I would rather put it in the SE category because it can not really be
accessed from an external client and does not handle a known protocol.
On Tue, Feb 3, 2009 at 14:24, <jb...@nanthrax.net> wrote:
> Guys,
>
> In parallel of the discussion "share components between Camel and SMX", I'm going to begin
> a servicemix-exec component.
>
> This component will be able to launch command (command and/or arguments can be provided in the NormalizedMessage), get the stdout/stderr stream and send back in the NMR (in a NormalizedMessage).
>
> Basicly, this component can be view :
> - as a binding component : if we consider the command outside SMX.
> - as a service engine : as the input and output going through the NMR, we can consider the command as a "business" logic and so the component is a service engine.
>
> I would like to have your feedback about this : do you consider this component as a BC or a SE ?
>
> My apologize is the question looks stupid :)
>
> Regards
> JB
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com