JSON with version 3.0.0

[Brian Kalbfus <bk...@akcourts.us>]

Hello,

I'm trying to see how synapse could be used as a JSON rest server.  Sample 158 claims to expose a SOAP web service as JSON, but the ant jsonclient code looks to be posting POX instead.  If I use curl to post JSON, the server errors and doesn't reply to the client.

Thank you,
Brian

Re: JSON with version 3.0.0

[Isuru Udana <is...@gmail.com>]

Hi Brian,

Can you please post the error you are getting while you are trying with
curl ?
And also the synapse configuration you are using.

Thanks.



On Sat, Sep 9, 2017 at 6:43 AM, Matthew Shaw <
Matthew.Shaw@ambulance.qld.gov.au> wrote:

> 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 hasn't
> really been touched since then.
>
> It's running on old tech ie. Axis2 and the world has moved on, particulary
> with rest and jax-rs.
>
> I ported my services across to apache camel running in an osgi container -
> karaf. Much happier and the user group support is very active.
>
> Sorry to sound negative, but that has been my experience with synapse. I
> guess you could go across to wso2 which is running on osgi anyway.
>
> -----Original Message-----
> From: Brian Kalbfus [mailto:bkalbfus@akcourts.us]
> Sent: Saturday, 9 September 2017 4:51 AM
> To: user@synapse.apache.org
> Subject: JSON with version 3.0.0
>
> Hello,
>
> I'm trying to see how synapse could be used as a JSON rest server.  Sample
> 158 claims to expose a SOAP web service as JSON, but the ant jsonclient
> code looks to be posting POX instead.  If I use curl to post JSON, the
> server errors and doesn't reply to the client.
>
> Thank you,
> Brian
> This email, including any attachments sent with it, is confidential and
> for the sole use of the intended recipient(s). This confidentiality is not
> waived or lost, if you receive it and you are not the intended
> recipient(s), or if it is transmitted/received in error.
>
> Any unauthorised use, alteration, disclosure, distribution or review of
> this email is strictly prohibited. The information contained in this email,
> including any attachment sent with it, may be subject to a statutory duty
> of confidentiality if it relates to health service matters.
>
> If you are not the intended recipient(s), or if you have received this
> email in error, you are asked to immediately notify the sender. You should
> also delete this email, and any copies, from your computer system network
> and destroy any hard copies produced.
>
> If not an intended recipient of this email, you must not copy, distribute
> or take any action(s) that relies on it; any form of disclosure,
> modification, distribution and/or publication of this email is also
> prohibited.
>
> Although the Queensland Ambulance Service takes all reasonable steps to
> ensure this email does not contain malicious software, the Queensland
> Ambulance Service does not accept responsibility for the consequences if
> any person's computer inadvertently suffers any disruption to services,
> loss of information, harm or is infected with a virus, other malicious
> computer programme or code that may occur as a consequence of receiving
> this email.
>
> Unless stated otherwise, this email represents only the views of the
> sender and not the views of the Queensland Government.
>
> ************************************************************
> ********************
>
> The content presented in this publication is distributed by the Queensland
> Government as an information source only. The State of Queensland makes no
> statements, representations or warranties about the accuracy, completeness
> or reliability of any information contained in this publication. The State
> of Queensland disclaims all responsibility and all liability (including
> without limitation for liability in negligence) for all expenses, losses,
> damages and costs you might incur as a result of the information being
> inaccurate or incomplete in any way, and for any reason reliance was placed
> on such information.
>
>


-- 
*Isuru Udana*
Senior Technical Lead




*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
<is...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*

RE: JSON with version 3.0.0

[Matthew Shaw <Ma...@ambulance.qld.gov.au>]

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 hasn't really been touched since then.

It's running on old tech ie. Axis2 and the world has moved on, particulary with rest and jax-rs.

I ported my services across to apache camel running in an osgi container - karaf. Much happier and the user group support is very active. 

Sorry to sound negative, but that has been my experience with synapse. I guess you could go across to wso2 which is running on osgi anyway.

-----Original Message-----
From: Brian Kalbfus [mailto:bkalbfus@akcourts.us] 
Sent: Saturday, 9 September 2017 4:51 AM
To: user@synapse.apache.org
Subject: JSON with version 3.0.0

Hello,

I'm trying to see how synapse could be used as a JSON rest server.  Sample 158 claims to expose a SOAP web service as JSON, but the ant jsonclient code looks to be posting POX instead.  If I use curl to post JSON, the server errors and doesn't reply to the client.

Thank you,
Brian
This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error.

Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited.

Although the Queensland Ambulance Service takes all reasonable steps to ensure this email does not contain malicious software, the Queensland Ambulance Service does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email.

Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government.

********************************************************************************

The content presented in this publication is distributed by the Queensland Government as an information source only. The State of Queensland makes no statements, representations or warranties about the accuracy, completeness or reliability of any information contained in this publication. The State of Queensland disclaims all responsibility and all liability (including without limitation for liability in negligence) for all expenses, losses, damages and costs you might incur as a result of the information being inaccurate or incomplete in any way, and for any reason reliance was placed on such information.