You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Kirk Spencer <ks...@playboox.com> on 2008/04/11 19:28:24 UTC
Drools Router vs. Camel SA
If the requirement is to be able to update routing without having to disrupt
services, can this be done with either component?
Which of these components could accomplish this with minimal interruption to
existing routing.?
--
Kirk Spencer
Playboox | Senior Software Engineer
Re: Drools Router vs. Camel SA
Posted by Kirk Spencer <ks...@playboox.com>.
Thank you very much. This helps with expectations.
On Mon, Apr 14, 2008 at 8:20 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> No, it's a good question ...
> Actually, none of these components can really update the rules at runtime
> without redeploying a service assembly. This is because the routing data
> is
> embedded in the artifact you deploy. However, if you redeploy the service
> assembly, the routes should be updated automatically wrt/ to the new ones
> deployed.
>
> On Mon, Apr 14, 2008 at 4:44 PM, Kirk Spencer <ks...@playboox.com>
> wrote:
>
> > Wrong question? or Wrong group to ask?
> >
> > If so could you direct me to the correct alias.
> >
> > On Fri, Apr 11, 2008 at 10:28 AM, Kirk Spencer <ks...@playboox.com>
> > wrote:
> >
> > > If the requirement is to be able to update routing without having to
> > > disrupt services, can this be done with either a Drools Router or
> Camel
> > > component?
> > >
> > > Which of these components could accomplish this with minimal
> > interruption
> > > to existing routing.?
> > >
> > > --
> > >
> > > Kirk Spencer
> > > Playboox | Senior Software Engineer
> > >
> >
> >
> >
> > --
> >
> > Kirk Spencer
> > Playboox | Senior Software Engineer
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
--
Kirk Spencer
Playboox | Senior Software Engineer
Re: Drools Router vs. Camel SA
Posted by Guillaume Nodet <gn...@gmail.com>.
No, it's a good question ...
Actually, none of these components can really update the rules at runtime
without redeploying a service assembly. This is because the routing data is
embedded in the artifact you deploy. However, if you redeploy the service
assembly, the routes should be updated automatically wrt/ to the new ones
deployed.
On Mon, Apr 14, 2008 at 4:44 PM, Kirk Spencer <ks...@playboox.com> wrote:
> Wrong question? or Wrong group to ask?
>
> If so could you direct me to the correct alias.
>
> On Fri, Apr 11, 2008 at 10:28 AM, Kirk Spencer <ks...@playboox.com>
> wrote:
>
> > If the requirement is to be able to update routing without having to
> > disrupt services, can this be done with either a Drools Router or Camel
> > component?
> >
> > Which of these components could accomplish this with minimal
> interruption
> > to existing routing.?
> >
> > --
> >
> > Kirk Spencer
> > Playboox | Senior Software Engineer
> >
>
>
>
> --
>
> Kirk Spencer
> Playboox | Senior Software Engineer
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Drools Router vs. Camel SA
Posted by Kirk Spencer <ks...@playboox.com>.
Wrong question? or Wrong group to ask?
If so could you direct me to the correct alias.
On Fri, Apr 11, 2008 at 10:28 AM, Kirk Spencer <ks...@playboox.com>
wrote:
> If the requirement is to be able to update routing without having to
> disrupt services, can this be done with either a Drools Router or Camel
> component?
>
> Which of these components could accomplish this with minimal interruption
> to existing routing.?
>
> --
>
> Kirk Spencer
> Playboox | Senior Software Engineer
>
--
Kirk Spencer
Playboox | Senior Software Engineer