[ https://issues.jboss.org/browse/TEIID-4374?page=com.atlassian.jira.plugin... ] Van Dillon edited comment on TEIID-4374 at 8/13/16 12:47 PM: ------------------------------------------------------------- Thanks for the help on this Ramesh. I suspected this wasn't a really bug. But I thought someone probably had a workaround. I'm not sure I fully understand the workaround you mention. If I'm trying to use an existing REST service (like RHQ) that has PUT operations with both input parameters (path, query, a mix) and a body (like the executeOperation operation); are you saying I should create a wrapper that includes the parameters and the body? What are the semantics for this? Do you just include the parameters as: [parameter name]=value How would you distinguish between path and query parameters? Is it then the responsibility of your code (the Swagger translator) or the Teiid OData interface code to unwrap this? Or does the OData implementation know how to unwrap it? The new dependency on apache.common.io comes from SwaggerParser. If you call read(String), it uses Swagger20Parser to load the file with org.apache.commons.io.FileUtils. was (Author: evdillon): Thanks for the help on this Ramesh. I suspected this wasn't a really bug. But I thought someone probably had a workaround. If we pass parameters in the body, is there any way to distinguish between path and query types? The new dependency on apache.common.io comes from SwaggerParser. If you call read(String), it uses Swagger20Parser to load the file with org.apache.commons.io.FileUtils. -- This message was sent by Atlassian JIRA (v6.4.11#64026)