Hi, With a jms receiver starter for example, I can use the sequencing key in advanced tab to sequence the process instances execution. Is the same possible with Rest or Soap web services using http transport? Thanks for your help. Regards

[Franck -]

Hi,

With a jms receiver starter for example, I can use the sequencing key in advanced tab to sequence the process instances execution.

Is the same possible with Rest or Soap web services using http transport?

 

Thanks for your help.

Regards

[Franck -]

Seems this is not possible for webservices, I don't understandf why. I thought that's because http transport, but this feature is available for http receiver, so why not an http based webservice (REST or SOAP) ?

[Andy-dont-use Pritchard]

Franck,

An HTTP receiver is Async by nature and responds to any request it's sent, whereas the JMS is able to process messages by leaving them in the messaging server until needed.

My only thought would be to have this as two steps ... An HTTP step that collects the message/data and places it into a JMS queue where you can use the sequencing key to determine the processing sequence.

HTH ... Andy

[Franck -]

Do you mean that we don't need this feature for sync features?

[Andy-dont-use Pritchard]

I'm not sure what your use case is here ..

There are situations where you need to process events/messages in a set sequence. You can do this with messages in a couple of ways.

HTTP based requests, tend to be orderless, or if they have an order that order is implied (ie part of the data).

If you want a HTTP app to process the requests it gets in some form of sequence then you're going to have to build that into your application.

What the usecase/scenario ? And why are you thinking of HTTP services to perform sequenced processing ?