Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

How to correctly pass NULL value in BPEL REST Adapter URI parameter

User_P5P8NSep 2 2020

I am running into an issue where I need pass a null value for a URI parameter when invoking a REST GET call from my BPEL process.

The request needs to look like one of the following:

          rest.url.com\restservice?param1=&param2=two

          rest.url.com\restservice?param1=%00&param2=two

param1 is accepted as null by the target system in one of these ways. Either way works correctly in test calls from SOAPUI, but when trying to accomplish this with the REST adapter I run into issues. My rest adapter is set up to use a wsdl and schema to create a request xml file that I create using xslt. If I pass it a null param1 (i.e. <param1/>) from the XML mapping it does not include the parameter in the URI at all and I get this:

          rest.url.com\restservice?&param2=two

On the other hand if I pass a string value representing NUL (<param1> %00</param1>) it seems to url encode it again for the special character '%' and the target system receives this instead

          rest.url.com\restservice?param1=%2500&param2=two

I have attempted to play around with attributes like disable-output-escape, required, default but have had no success.

Comments
Post Details
Added on Sep 2 2020
1 comment
604 views