[jira] [Updated] (OLINGO-1160) How to use features such as $filter $top in Olingo V2
[ https://issues.apache.org/jira/browse/OLINGO-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ziyi Jiang updated OLINGO-1160: --- Description: When I call a function import of which the datatype is Complex and it joins the two table, I get the following output showing system query is not compatible when I use $top function. Same result returned when using $filter function. Running environment: Windows 10 Tomcat 8.0.3 Olingo V2 2.0.7 http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;> System query option '$top' is not compatible with the return type. Thanks and appreciated! was: When I call a function import of which the datatype is Complex and it joins the two table, I get the following output showing system query is not compatible when I sue $top function. So does it using $filter function. Running environment: Windows 10 Tomcat 8.0.3 Olingo V2 2.0.7 http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;> System query option '$top' is not compatible with the return type. Thanks and appreciated! > How to use features such as $filter $top in Olingo V2 > - > > Key: OLINGO-1160 > URL: https://issues.apache.org/jira/browse/OLINGO-1160 > Project: Olingo > Issue Type: Question >Affects Versions: V2 2.0.7 >Reporter: Ziyi Jiang >Priority: Critical > > When I call a function import of which the datatype is Complex and it joins > the two table, I get the following output showing system query is not > compatible when I use $top function. > Same result returned when using $filter function. > Running environment: > Windows 10 > Tomcat 8.0.3 > Olingo V2 2.0.7 > http://schemas.microsoft.com/ado/2007/08/dataservices/metadata;> > > > System query option '$top' is not compatible with the return type. > > > Thanks and appreciated! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OLINGO-1159) Enhancements to Bound Actions in V4
[ https://issues.apache.org/jira/browse/OLINGO-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1159. --- Resolution: Fixed > Enhancements to Bound Actions in V4 > --- > > Key: OLINGO-1159 > URL: https://issues.apache.org/jira/browse/OLINGO-1159 > Project: Olingo > Issue Type: Bug > Components: odata4-client, odata4-server >Affects Versions: (Java) V4 4.3.0 >Reporter: Ramya > > Support for binding parameter is limited to Entitytype and Entity Collection. > When the binding parameter includes additional segments like type cast to > derived types or complex types it doesn't work. > A fix is required in the Uri Parser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-1159) Enhancements to Bound Actions in V4
[ https://issues.apache.org/jira/browse/OLINGO-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119684#comment-16119684 ] Ramya commented on OLINGO-1159: --- The fix is part of the commit https://git-wip-us.apache.org/repos/asf?p=olingo-odata4.git;a=commit;h=d4f1b73875e8c5a474d7265f9d36c57854bca800 > Enhancements to Bound Actions in V4 > --- > > Key: OLINGO-1159 > URL: https://issues.apache.org/jira/browse/OLINGO-1159 > Project: Olingo > Issue Type: Bug > Components: odata4-client, odata4-server >Affects Versions: (Java) V4 4.3.0 >Reporter: Ramya > > Support for binding parameter is limited to Entitytype and Entity Collection. > When the binding parameter includes additional segments like type cast to > derived types or complex types it doesn't work. > A fix is required in the Uri Parser. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (OLINGO-752) Add support for "+" sign as a separator in addition to %20 for URLs
[ https://issues.apache.org/jira/browse/OLINGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119614#comment-16119614 ] Ronny Bremer commented on OLINGO-752: - Thank you very much Archana for your fix. It looks great to me and I will give you feedback after we tried it. Yours, Ronny > Add support for "+" sign as a separator in addition to %20 for URLs > --- > > Key: OLINGO-752 > URL: https://issues.apache.org/jira/browse/OLINGO-752 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Affects Versions: V2 2.0.4, (Java) V4 4.0.0-beta-03 >Reporter: Ronny Bremer >Priority: Minor > Attachments: 0002-OLINGO-752-Treat-as-space-in-Decoder.patch > > > Some well-known OData client libraries, such as JQuery, are using the > incorrect encoding for URLs sent to OLingo based OData v2 services. > According to the OData V2 standard, the separator for encoded URLs is %20. > However, in many cases when developers talk about "URL encoding", they use > Java functions like "URLEncoder.encode()" to encode the parameters for their > HTTP request. JQuery seems to utilise a similar function in JavaScript. > Now these functions are based on the HTTP forms encoding standard, so they > use "+" as a separator. > If would be small but grateful addition to the OLingo URI parser to accept > both separator characters. Maybe with a config option to follow the standard > (so only accept %20) or to be more relaxed (and accept both). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OLINGO-752) Add support for "+" sign as a separator in addition to %20 for URLs
[ https://issues.apache.org/jira/browse/OLINGO-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana Rai resolved OLINGO-752. Resolution: Resolved > Add support for "+" sign as a separator in addition to %20 for URLs > --- > > Key: OLINGO-752 > URL: https://issues.apache.org/jira/browse/OLINGO-752 > Project: Olingo > Issue Type: New Feature > Components: odata2-core >Affects Versions: V2 2.0.4, (Java) V4 4.0.0-beta-03 >Reporter: Ronny Bremer >Priority: Minor > Attachments: 0002-OLINGO-752-Treat-as-space-in-Decoder.patch > > > Some well-known OData client libraries, such as JQuery, are using the > incorrect encoding for URLs sent to OLingo based OData v2 services. > According to the OData V2 standard, the separator for encoded URLs is %20. > However, in many cases when developers talk about "URL encoding", they use > Java functions like "URLEncoder.encode()" to encode the parameters for their > HTTP request. JQuery seems to utilise a similar function in JavaScript. > Now these functions are based on the HTTP forms encoding standard, so they > use "+" as a separator. > If would be small but grateful addition to the OLingo URI parser to accept > both separator characters. Maybe with a config option to follow the standard > (so only accept %20) or to be more relaxed (and accept both). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
