[
https://issues.apache.org/jira/browse/OLINGO-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
M Carissimi resolved OLINGO-140.
--------------------------------
Resolution: Not A Problem
Hi Stephan,
thank you for your responses, sounds like we won't be able to use Function
Imports for functions that require binary data to be passed from the consumer
to the producer.
It might be worth considering this use case when updating the OData
specification in future.
Cheers
Miki
> Function Import support for binary data
> ---------------------------------------
>
> Key: OLINGO-140
> URL: https://issues.apache.org/jira/browse/OLINGO-140
> Project: Olingo
> Issue Type: Question
> Affects Versions: V2 1.0.0
> Reporter: M Carissimi
> Assignee: Stephan Klevenz
>
> Hello,
> I have created a FucntionImport for one of my EnityTypes which has a single
> parameter of type Edm.Binary. This is how the FunctionImport is shown on the
> metedata:
> <FunctionImport Name="Import_Readings"
> ReturnType="esys_producer.ES_IMPORT_READINGS" EntitySet="ES_IMPORT_READINGS"
> m:HttpMethod="POST">
> <Parameter Name="Import File" Type="Edm.Binary"/>
> </FunctionImport>
> I now need to create an OData consumer which is able to invoke the
> FunctionImport. I have created an html form where a file can be uploaded
> which then invokes a Java servlet. The servlet uses odata4j to connect to the
> OData service and invokes the function. Unfortunately the odata4j library
> does not allow to set the property type as a byte array, which is what would
> be required for a Binary parameter.
> I now have a few questions:
> - is it OK to have Binary parameters in a FunctionImport?
> - when inoking a FunctionImport, do all the parameter values get set on the
> URL? If so, will the limit on size of a URL stop us from sending a large
> binary parameter to a FunctionImport?
> - how can I create a client similar to the one described above using the
> Olingo library?
> Regards
> Miki
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
