Re: [Dev] ESB Blocking call mediator

Hi Godwin, We can try the following to maintain the URL in registry. 1. Create a registry entry with the url. 2. Use call mediator with default endpoint. 3. Use get-property( ​'registry'​ , property ​ path​ ) ​ to get the value. 4. Set TO header before using call in

Re: [Dev] ESB Blocking call mediator

Hi Malaka, There is a template with a parameter as registry resource for backend endpoint. So inside the template we need to call backend endpoint using the parameter pass into template. Hope you understand my requirement. Thanks Godwin On Thu, Jun 9, 2016 at 12:37 AM, Malaka Silva

Re: [Dev] ESB Blocking call mediator

Hi Godwin, For using the key-expression feature, shall we get the exact use case that you are trying to implement? On Wed, Jun 8, 2016 at 7:55 PM, Godwin Shrimal wrote: > Hi Kathees, > > My requirement is to use key-expression in blocking mode. > > @Isuru : Do we have any

Re: [Dev] ESB Blocking call mediator

Hi Kathees, My requirement is to use key-expression in blocking mode. @Isuru : Do we have any workaround/alternatives to achieve this ? Thanks Godwin On Tue, Jun 7, 2016 at 11:22 PM, Kathees Rajendram wrote: > Hi Godwin, > > Call mediator blocking mode supportes indirect

Re: [Dev] ESB Blocking call mediator

Hi Godwin, Call mediator blocking mode supportes indirect URL with key as you mensioned above. Can you define the key expression in the endpoint. @Isuru Yes, call mediator with the combination of blocking=true and key-expression in endpoint is not supported directly. We can use above

Re: [Dev] ESB Blocking call mediator

Hi Godwin, I think key-expressions are not supported in blocking mode. @Kathees, Can you please confirm ? Thanks. On Wed, Jun 8, 2016 at 3:08 AM, Godwin Shrimal wrote: > Hi All, > > When I use call mediator in my sequence as below it gives error [1]. > > > > > > > If I

[Dev] ESB Blocking call mediator

Hi All, When I use call mediator in my sequence as below it gives error [1]. If I change the code as any of below, its works fine. Do we have a problem in Call mediator with the combination of *blocking=true *and *key-expression *in endpoint ? [1]