Yes of course. Pass them as  a request property and on the operation do 

..Adapter.FilePath = request.FP

..Adapter.FileName = request.FN

Keep the second version

and build that List of objects with - As list of MyPackage.MyClass

list.insert(obj1)

list.insert(obj2)
and so on..

Please feel free to send me sample code and I can make it for you too. 

It used to work on IRIS 2019.. Now I don't remember what version of 2019. I think it was 2019.1.1 but can't bet on it.

Can you please paste the openapi spec for that ?

Another factor which I forgot to mention was that the Path was working past 2 years with the openapi spec I had, it only stopped working on the latest 2020 version.

There are couple of options to do this.

1. You can extend your class &JSON.Adaptor, it will do it for you with inbuilt logicaldtodisplay methods

2. Create another request class and do your transformations

3. Before calling the json convert to stream methods, transform the object's field with a ZDT.

 

This is a sample spec. note this line

"in":"query",
Now I have to call this rest endpoint as 

http://localhost:52774/csp/restapp/Demo?country=uk

however earlier i had
"in":"path"   
and was calling rest endpoint as 

http://localhost:52774/csp/restapp/Demo/uk.

Now in=path does not even compile. Thus just curious why .
----------------------------------------------------------------


XData OpenAPI [ MimeType = application/json ]
{
{
"swagger":"2.0",
"info":{
"title":"O",
"version":"1"
},
"schemes":[
"http",
"https"
],
"consumes":[
"application/json]"
],
"produces":[
"application/json]"
],
"paths":{

"/Demo":{
"get":{
"summary":"Get Demo ",
"description":"Demo ",
"operationId":"GETDemo",
"x-ISC_CORS":true,
"consumes":[
"application/json]",
"text/html]"
],
"produces":[
"application/json]",
"text/html]"
],
"parameters":[
{
"name":"country",
"type":"string",
"in":"query",
"description":"Country Name",
"allowEmptyValue": true
} ],
"responses":{
"200":{
"description":"Returns Country",
"schema": {
"type":"string"
}
}
}
}
}
}
}
}