Products Products
Support & Forums Support & Forums
Compliance Testing Compliance Testing
Labs & Sandboxes Labs & Sandboxes
Program Program
Co-Marketing Co-Marketing
Avaya Experience Platform Avaya Enterprise Cloud Avaya Client SDK Avaya Aura Platform See All Products Find Developer Resources

Avaya Experience Platform

Overview Interfaces Learning Support Options Compliance Testing

Avaya Enterprise Cloud

Overview Interfaces Learning Support Options Compliance Testing

Avaya Client SDK

Overview Programming Docs Developer Downloads Licensing Support & Testing

Avaya Aura Platform

Application Enablement Services Communication Manager Presence Services Snap-in Session Manager System Manager Session Border Controller
About DevConnect Support Submit Support Tickets Support Forums Other Support Options

About DevConnect Support

Support Options Support FAQs Supported Platforms and Interfaces

Submit Support Tickets

Procured System Support
For procurement issues or questions Remote Lab Support
For issues and questions related to DevConnect remote labs Membership & Program Support
For membership and program benefits questions General Support
For general issues not covered by the other support tickets

Support Forums

Avaya Client SDK AEServices DMCC APIs AEServices JTAPI AEServices Web Services Avaya Workspaces Avaya Experience Platform Orchestration Designer All Forums

Other Support Options

Product Notices Non-DevConnect Support Resources

Compliance Testing

About Compliance Testing Compliance Tested Solutions

About Compliance Testing

Compliance Testing Overview Avaya Interfaces Eligible For Testing Compliance Testing FAQs Compliance Testing Guide(s) (PDF)

Compliance Tested Solutions

DevConnect Marketplace Search Applications Notes

Labs & Sandboxes

Remote Labs Procurement Benefits

Remote Labs

Remote Labs Overview Avaya Aura Session Manager Avaya Aura AE Services & Communication Manager Self Services (Experience Portal) Avaya Proactive Outreach Manager Avaya Contact Center Elite

Procurement Benefits

About DevConnect Procurement Access/View Procurement Catalog Procurement FAQs DevConnect Procured System Support

Program

Program Overview Program Benefits Membership Options

Program Overview

DevConnect Membership Levels DevConnect Program Guide (PDF) DevConnect Program FAQs

Program Benefits

Membership Benefits DevConnect Procurement Co-marketing

Membership Options

Manage My Portfolio/Solutions Manage My Profile

Co-Marketing

Co-Marketing Benefits Relationship Benefits

Co-Marketing Benefits

Co-Marketing Overview Logos Marketplace Co-branded Collateral Select Product Program

Relationship Benefits

Social Media 8-and-Out Podcasts Sponsorships Advertising

Author Message
16/01/2019 23:13:05
Subject: How to write request in non-XML/JSON format
#1
YoshihikoTashiro
Joined: Mar 10, 2014
Messages: 22
Offline
Dear experts,
I'd like to write URL-encoded request in 'Message Body' in Web Service Operational File (REST) like:
token=abcdefg&phonenumber=12345890

I write it as-is then OD shows error message "Content is not allowed in prolog".
Any keyword is needed like 'JSON' for JSON format?

Thank you in advance.
PM
17/01/2019 12:54:21
Subject: Re:How to write request in non-XML/JSON format
#2
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
You can use Java code to URL encode it in the Java class for the REST operation. Put the custom code below the line "//}}END:CLASS:CONSTRUCTOR" so that it won't get overwritten by the code generator.
PM
17/01/2019 19:10:52
Subject: Re:How to write request in non-XML/JSON format
#3
YoshihikoTashiro
Joined: Mar 10, 2014
Messages: 22
Offline
Hi Wilson,
Thank you for your response.

I'd like to make sure one thing -
does WSO object allow only XML and JSON in 'Message Body'?

Regards,
PM
17/01/2019 22:15:17
Subject: Re:How to write request in non-XML/JSON format
#4
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
The problem is not whether it supports XML/JSON. It should support any text. The message body is treated like regular text being sent over the web. However sending text over the web means certain characters has to be escaped or URL encoded. That's what the error seems to me. I suspect it's the "&" character here.
PM
17/01/2019 23:39:49
Subject: Re:How to write request in non-XML/JSON format
#5
YoshihikoTashiro
Joined: Mar 10, 2014
Messages: 22
Offline
I'm afraid the error did not disappear even I got rid of all signs ('&', '%' and '=') from Message Body text.
As far as I tested with OD 7.2.1, the error disappeared only when Message Body
- begins with start tag and ends with end tag
- begins with 'JSON'

Regards,
PM
18/01/2019 00:52:34
Subject: Re:How to write request in non-XML/JSON format
#6
WilsonYu
Joined: Nov 6, 2013
Messages: 3950
Offline
Sorry, I've never done any REST call that requires a message body. I wasn't sure. Since this goes through the Axis 2 API, and it looks like the error comes from there, I guess Axis2 needs it to be XML or JSON format.
PM
18/01/2019 00:58:46
Subject: Re:How to write request in non-XML/JSON format
#7
YoshihikoTashiro
Joined: Mar 10, 2014
Messages: 22
Offline
Thank you for your reply.
I got it.
PM
Go to:   
Mobile view