The REST web service returns a java object java.util.Map as a part of the response. This map contains keys that have a "-" in it .. example , .. "char-encoding". how do i deal with these type of incoming members of the JSON response in terms of properties in pega. The wizard cannot make properties named with a "-" in them and eventually causes the connect-rest call to fail when invoked.
I've currently worked around this issue by removing the Map from the REST response. But this would have been a real issue if I had no control over the web service. Because .... the connect call doesn't fail after the response is received. It fails when the call is made.
Just adding a note before someone gets this idea and thinks that it's an appropriate response ... I CANNOT change the response type to xml. That is just NOT an option. In fact going back to xml is like going back in time. So... a BIG NO to xml.
While it is true that the wizard cannot generate properties with hyphens in the name, it may have set a "qualifier" on the Property records which contain the original name. When the connector is called, it should be using the qualifier to map from the "real" name to the property name.
Please open one of the properties and take a look to see if it has a qualifier set on it.
Thanks for your response. I am using version 7.1.8. The wizard does create qualifiers with the property pzExternalName and this is used at runtime when the connector makes the call to the web service. This resolves the problem. I wasn't aware that this property qualifier feature existed in pega.