tapvanvn / odata4j

Automatically exported from code.google.com/p/odata4j
0 stars 0 forks source link

Improve Function Call Support #182

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Improve function call support including following features:

- parameter support for single and double
- simple return types
- complex return type
- entity return type
- collection based return type

Original issue reported on code.google.com by stephan....@googlemail.com on 4 Jun 2012 at 3:52

GoogleCodeExporter commented 9 years ago
Sorry Stephan, are you able to use function? 

Original comment by porcelli...@gmail.com on 11 Jun 2012 at 6:05

GoogleCodeExporter commented 9 years ago
There is a basic function call support impelemented. However to be full OData 
2.0 compliant I'm improving code here: 

https://bitbucket.org/sklevenz/odata4j-function

That task will be finished soon.

Original comment by stephan....@googlemail.com on 12 Jun 2012 at 6:27

GoogleCodeExporter commented 9 years ago
Acceptance Test:

http://code.google.com/p/odata4j/source/browse/odata4j-fit/src/test/java/org/oda
ta4j/test/integration/function/FunctionImportTest.java?spec=svn4b22e638294c25857
ac631fbdc724eb334a229c4&r=4b22e638294c25857ac631fbdc724eb334a229c4

Original comment by stephan....@googlemail.com on 13 Jun 2012 at 1:03

GoogleCodeExporter commented 9 years ago
Extend function call support for all http methods (put, post, delete ...)

Original comment by stephan....@googlemail.com on 29 Jun 2012 at 9:19

GoogleCodeExporter commented 9 years ago
Issue 131 has been merged into this issue.

Original comment by stephan....@googlemail.com on 19 Sep 2012 at 6:55

GoogleCodeExporter commented 9 years ago
User feedback:

Function call POST, PUT, MERGE, PATCH, DELETE do currently not support function 
parameter. 

A fixing commit for 0.8.0-SNAPSHOT is following...

Original comment by stephan....@googlemail.com on 27 Sep 2012 at 4:38

GoogleCodeExporter commented 9 years ago
Hi, with fix of this issue support for parsing values like "2.0" to double 
(without 'd') was gone. Is it intentional? Is adding f/d to expression for 
simple double value mandatory in odata?

Removed piece of code:
// double literal: 2.0
if (tokens.size() == 3 && tokens.get(0).type == TokenType.NUMBER && 
tokens.get(1).type == TokenType.SYMBOL && tokens.get(1).value.equals(".") && 
tokens.get(2).type == TokenType.NUMBER) { ...

Original comment by vaclav.h...@gmail.com on 16 Oct 2012 at 8:39