First of all, I want to thank the Google GData API engineers for their good work, and I would like to mention that this question is not intended to criticize anything. It just points to things.
Can anyone explain this to me? As far as I can see, the developers of the java-client library google api invent the wheel. This is like creating a new JDK for a Java project, because the abdera client does what the google api client library does, and the server functions and abdera adapters can also be used for many things, such as write persistence and many others.
I am aware that the Google data protocol is a small specific publication of atoms, but if you need to use some of the fancy extensions and functions that Apache Abdera offers for this protocol, it is better not to use the Google api client library and implement the client from scratch with Abdera ... And I’m sure that in many cases its functions, such as the Abdera JCR adapter, would become very convenient for Google documents, Google toolkits for translators, and almost for most others.
Now it’s great that there is a google api client library for Google Docs, but what will I do with the documents and answers to the atom feed? I believe that in more than half of cases there is a repository or database on the other side. And in this case, abdera is required, and not simple google api clients that only sort / untie feeds ...
In fact, all of the Google APIs have something that is needed. It would be wise if Google decided to invest in improving or integrating Abdera ... It's not ... Especially given the very well-known fact in software development, this second release is usually rewritten from scratch. Apache Abdera is a mature project with 5 years of existence, used by many applications.
, pull, , XML-, . Xmlpull.org 6 , StAX api. stax.codehaus.org, JRE, Axiom Apache , , woodstox.codehaus.org , ?
java- google api client , google apis, , . , , - , Reinventing the wheel 0 gdata-java-client google-api-client-java.
, google API- , , , , ?: -)
, , ... , GData JSON, !