|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Handling Special characters in JSON |
« View previous topic :: View next topic » |
Author |
Message
|
stoney |
Posted: Thu Jan 28, 2016 6:23 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013 Posts: 140
|
|
Back to top |
|
|
Vitor |
Posted: Thu Jan 28, 2016 6:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
stoney wrote: |
Yes, that's correct! |
I correctly understood a JSON explanation! I'm therefore an expert on all aspects of REST and API Management!
Thank you for your kind confirmation. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
mqjeff |
Posted: Thu Jan 28, 2016 6:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
stoney wrote: |
If you use a JSON parser that is compliant with the specification |
.... Or why I asked to see the error on the Azure side...
"Existing JSON Parser? Why bother, we can just write our own!"
vitor wrote: |
I correctly understood a JSON explanation! I'm therefore an expert on all aspects of REST and API Management! |
Excellent. For your next trick, design and implement a REST version of this SOAP API with hundreds of requests per operation, consisting of thousands of fields each... Without access to the WSDL. _________________ chmod -R ugo-wx / |
|
Back to top |
|
|
sumit |
Posted: Thu Jan 28, 2016 7:14 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006 Posts: 398
|
Thanks stoney for explaining that!
mqjeff wrote: |
.... Or why I asked to see the error on the Azure side...
"Existing JSON Parser? Why bother, we can just write our own!" |
Well, I came to know yesterday that there is a C# application which is exposing the REST service and from there, requests message go to Azure.
Logs in this C# application are not very detailed one.
However, thanks for the pointer. Now we will see if C# application is using a proper JSON parser or not. _________________ Regards
Sumit |
|
Back to top |
|
|
Vitor |
Posted: Thu Jan 28, 2016 7:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Excellent. For your next trick, design and implement a REST version of this SOAP API with hundreds of requests per operation, consisting of thousands of fields each... Without access to the WSDL. |
I'll do that, and with swagger _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
stoney |
Posted: Thu Jan 28, 2016 7:43 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013 Posts: 140
|
Vitor wrote: |
mqjeff wrote: |
Excellent. For your next trick, design and implement a REST version of this SOAP API with hundreds of requests per operation, consisting of thousands of fields each... Without access to the WSDL. |
I'll do that, and with swagger |
In YAML, right? |
|
Back to top |
|
|
Vitor |
Posted: Thu Jan 28, 2016 7:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
stoney wrote: |
Vitor wrote: |
mqjeff wrote: |
Excellent. For your next trick, design and implement a REST version of this SOAP API with hundreds of requests per operation, consisting of thousands of fields each... Without access to the WSDL. |
I'll do that, and with swagger |
In YAML, right? |
Exactly the same standard I use for my Java:
Years Away, Might Leak
_________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|