Active
Project:
oData
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Jan 2014 at 10:33 UTC
Updated:
29 May 2015 at 16:36 UTC
Jump to comment: Most recent
I am in the middle of rewriting the whole code to be both Drupal and Views 3.x friendly.
A version 1.2 is going to be released within next weeks that will support every oData endpoint.
Use the development version at your own risk.
Remaining tasks are:
Comments
Comment #1
sfcamil commentedFirst of all, nice to see you again and sorry for my English ;) and remember that I'm not an programmer.
Just some modifications made by me probably a good idea to start :
odata_handler_field_date.inc
- Sometimes $values->{$this->real_field} can be null
- Probably the version of my OData server (java-jpa-hibernate-oracle) sends me the date on other format? deleted double intval(intval
odata_handler_field_numeric.inc
- Copied from Views module function render($values) and modified like this. I have problems with long (oid) returned by my server.
data_plugin_query_odata.inc
- function query - initial was: function query($view, $get_count = FALSE) it's not like views3 . changed to function query($get_count = FALSE) and get view from:
$view = views_get_current_view();- see that odata have a protocol to query conditional like substringof, endswith, startswith but here we missing the “eq true” at the end of condition (OData proto)
Added this to alter the query:
- for me the results is in $reply['results'] not in $reply
- later in the same function a do this, but I don’t remember why:
odata_metadata.inc
- function odata_xml2array2 eliminate m: from OData response. Probably not the right solution but it’s ok for me.
Comment #2
apanag commentedHi there,
Just a quick heads up: I just finished rewriting the admin UI to be based on ctools multiform wizard instead of the ugly old code there. Next in my todo list is editing and rewriting the XML Parser (which hopefully will resolve your bug in #2124769: Namespace prefix m for IsDefaultEntityContainer).
After that I am going to see your suggestions. Really appreciate your feedback :-) Unfortunately Views code is in progress yet, so some features are missing.
PS. If your odata endpoint is a public one, can you type it here to run some additional tests?
Thank you!
Comment #3
apanag commentedComment #4
sfcamil commentedHi,
My endpoint it’s not public but I can give you a possibility to test but not here. I don’t know if Drupal have the possibility to send private message if not you have another possibility to send you a private message? (facebook, twitter ...)
Thanks !
Comment #5
apanag commentedHi all,
hopefully tomorrow I will update the development version. There is a new custom oData parser, that will provide a class to handle odata objects and will be enhanced during future development As said earlier, the admin UI is completely rewritten, and the whole schema is saved in the db to avoid extra unnecessary requests. I guess some Ajax magic can be included there, but something like that goes later in the list.
Next thing is to implement the complex entities and to start writing some unit tests.
@sfcamil: Please use the contact form, in my Drupal profile.
Comment #6
apanag commentedComment #7
apanag commentedI just pushed some commits that correct all the errors mentioned here.
Also there are some tests mostly for the oData admin UI for now.
Next is integration of complex fields and contextual filters.
:-)
Comment #8
apanag commentedHi all,
The latest development code supports complex fields and contextual filters. Next in the todo list is to fully test them in order to prevent any bugs.
If anyone is willing to play with that code and report any bugs he/she might encounter, that would be great.
In the meantime I will create write SimpleTests for the Views UI.
PS. Requests for further development are more than welcome.
:-D
Comment #9
apanag commentedComment #10
brooke_heaton commentedDoes the module support ODATA API Token authentication? I have not been able to get this to work with tokens. Further information here: https://stage.fra.dot.gov/MasterWebService/PublicAPI/v1/Develop/QuickSta...
Comment #11
wub commentedWhat is the current status of this project? It seems like there hasn't been any activity in quite a while.
Comment #12
apanag commentedThat's true @wub. All my active projects on the oData framework have been replaced and had to allocate my time to other tasks.