You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by kbarlow <ke...@cable.comcast.com> on 2009/09/29 21:32:31 UTC

Flow Initilization

Hiyas,

I am writing my first service flow and there is something I am a little
confused over that I was hoping someone could clarify:

My intent is to publish a pipeline type process.  Essentially, there will be
a series of queues and services and each service reads from a designated
queue and writes its response to the next queue in line.  

The confusion results in configuring the service that exposes the process
entry.  All it should do is receive a message and place it in the 1st queue.
To do this it would appear as though I should use the <http:provider />
component to establish the service (connect to a backend service) and the
<http:consume /> component to make it publically accessible.  What I don't
understand is how do I make the service response route to the JMS queue? 
The <http:consume /> component does not allow you to route the output
returned from the <http:provider /> component to another component (whether
it be a jms queue or a router)...  What is the proper way to achieve this
setup?

The basic example lists this as a use case but does not provide the
configuration setup used to achieve such an execution...

Thanks.

Keith
-- 
View this message in context: http://www.nabble.com/Flow-Initilization-tp25669419p25669419.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Flow Initilization

Posted by kbarlow <ke...@cable.comcast.com>.
Yes... I think it does.  I will give it a try and see what I come up with.

Thanks.

keith


Dave Stanley wrote:
> 
> So assuming you want to use http you might have something like this:
> 
>  <http:endpoint service="test:httpProvider"
>                  endpoint="providerEndpoint"
>                  role="provider"
>                  locationURI="http://localhost:9000/outgoing/customer"
>                  />
> 
>   <http:endpoint service="test:httpConsumer"
>                  endpoint="consumerEndpoint"
>                  targetService="test:routingSlip"
>                  targetEndpoint="test:routingSlipEndpoint"
>                  role="consumer"
>                  locationURI="http://localhost:9100/incoming/customer"
>                  defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
>                  />
> 
> and the an eip SU that uses a routing slip
> 
>   <eip:static-routing-slip service="test:routingSlip"
> endpoint="routingSlipEndpoint">
> 
>      <eip:targets>
>         <eip:exchange-target service="test:httpProvider" />
>         <eip:exchange-target service="test:jmsInOutMepTarget" />
>     </eip:targets>
>   </eip:static-routing-slip>
> 
> Hope that helps
> /Dave
> 
> 
> 
> On Tue, Sep 29, 2009 at 3:32 PM, kbarlow
> <ke...@cable.comcast.com>wrote:
> 
>>
>> Hiyas,
>>
>> I am writing my first service flow and there is something I am a little
>> confused over that I was hoping someone could clarify:
>>
>> My intent is to publish a pipeline type process.  Essentially, there will
>> be
>> a series of queues and services and each service reads from a designated
>> queue and writes its response to the next queue in line.
>>
>> The confusion results in configuring the service that exposes the process
>> entry.  All it should do is receive a message and place it in the 1st
>> queue.
>> To do this it would appear as though I should use the <http:provider />
>> component to establish the service (connect to a backend service) and the
>> <http:consume /> component to make it publically accessible.  What I
>> don't
>> understand is how do I make the service response route to the JMS queue?
>> The <http:consume /> component does not allow you to route the output
>> returned from the <http:provider /> component to another component
>> (whether
>> it be a jms queue or a router)...  What is the proper way to achieve this
>> setup?
>>
>> The basic example lists this as a use case but does not provide the
>> configuration setup used to achieve such an execution...
>>
>> Thanks.
>>
>> Keith
>> --
>> View this message in context:
>> http://www.nabble.com/Flow-Initilization-tp25669419p25669419.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/Flow-Initilization-tp25669419p25688278.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Flow Initilization

Posted by Dave Stanley <ds...@gmail.com>.
So assuming you want to use http you might have something like this:

 <http:endpoint service="test:httpProvider"
                 endpoint="providerEndpoint"
                 role="provider"
                 locationURI="http://localhost:9000/outgoing/customer"
                 />

  <http:endpoint service="test:httpConsumer"
                 endpoint="consumerEndpoint"
                 targetService="test:routingSlip"
                 targetEndpoint="test:routingSlipEndpoint"
                 role="consumer"
                 locationURI="http://localhost:9100/incoming/customer"
                 defaultMep="http://www.w3.org/2004/08/wsdl/in-out"
                 />

and the an eip SU that uses a routing slip

  <eip:static-routing-slip service="test:routingSlip"
endpoint="routingSlipEndpoint">

     <eip:targets>
        <eip:exchange-target service="test:httpProvider" />
        <eip:exchange-target service="test:jmsInOutMepTarget" />
    </eip:targets>
  </eip:static-routing-slip>

Hope that helps
/Dave



On Tue, Sep 29, 2009 at 3:32 PM, kbarlow <ke...@cable.comcast.com>wrote:

>
> Hiyas,
>
> I am writing my first service flow and there is something I am a little
> confused over that I was hoping someone could clarify:
>
> My intent is to publish a pipeline type process.  Essentially, there will
> be
> a series of queues and services and each service reads from a designated
> queue and writes its response to the next queue in line.
>
> The confusion results in configuring the service that exposes the process
> entry.  All it should do is receive a message and place it in the 1st
> queue.
> To do this it would appear as though I should use the <http:provider />
> component to establish the service (connect to a backend service) and the
> <http:consume /> component to make it publically accessible.  What I don't
> understand is how do I make the service response route to the JMS queue?
> The <http:consume /> component does not allow you to route the output
> returned from the <http:provider /> component to another component (whether
> it be a jms queue or a router)...  What is the proper way to achieve this
> setup?
>
> The basic example lists this as a use case but does not provide the
> configuration setup used to achieve such an execution...
>
> Thanks.
>
> Keith
> --
> View this message in context:
> http://www.nabble.com/Flow-Initilization-tp25669419p25669419.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>