REST API returning an error message to client

Hi All, Running synapse3 with a rest api. I have a faultsequence defined which is being invoked when my backend call returns an error. The 500 internal server error is being sent back to my client, however, I cannot seem to send my error message back. Here is my xml config fragment

RE: REST API returning an error message to client - SOLVED

For anyone interested... Add the to your faulsequence. By default this is property is set for GET requests. Cheers, Matt. -Original Message- From: Matthew Shaw [mailto:matthew.s...@ambulance.qld.gov.au] Sent: Friday, 11 August 2017 1:43 PM To: user@synapse.apache.org Subject: REST

class mediator and error handling

Hi, There appears to be a bug in the class mediator when using a try catch. It goes into the catch statement when I force an error, however my code never executes. It jumps straight into ClassMediator catch statement. Here is my mediator code: public class GetTimesheetMediator implements Media

RE: class mediator and error handling

ene Schwarb [mailto:rene.schw...@ipt.ch] Sent: Monday, 14 August 2017 2:41 PM To: user@synapse.apache.org Subject: Re: class mediator and error handling Hi Matt what's in the Exception e? René 2017-08-14 2:05 GMT+02:00 Matthew Shaw : > Hi, > > There appears to be a bug in the cl

Java DSL

Hi All, Any idea if there are plans to provide a fluent api / dsl in the future, rather than just xml config? I'm happy to get involved and help, if this is on the dev roadmap. Cheers, Matt. This email, including any attachments sent with it, is confidential and for the sole use of the intende

properties

Hi, Is there a way to configure app like properties from a properties file and make them available to my flows via the mediator? Ie. I'd like to have a properties file like Property.a=123 Property.b=456 Cheers, Matt. This email, including any attachments sent with it, is confidential and for t

exception handling

Hi All, I've got service A invoking service B via a callout. (Proxy services) Service B throws a fault via the following fault sequence and returns the following soap fault. 2017-08-17 09:21:47,193 [-] [PassThroughMessageProcessor-227] INFO LogMediator To: /services/TimesheetEntityProxy.Times

RE: exception handling - UPDATE

I've added the following to the target input sequence on my service A, but still no joy... -Original Message- From: Matthew Shaw [mailto:matthew.s...@ambulance.qld.gov.au] Sent: Thursday, 17 August 2017 9:38 AM To: user@synapse.apache.org Subject: exception handling Hi All,

RE: JSON with version 3.0.0

Hi Brian, The best advice I can give you is ditch synapse. I've been working with it for the last 6 months and the user group is dead. Basically, the core developers are working on a commercial thing called ultra esb. Synapse was a spin off of wso2's first attempt at and esb back in 2006 and it