Eugen Deutsch created OLINGO-1541:
-------------------------------------
Summary: Samples seem to be outdated
Key: OLINGO-1541
URL: https://issues.apache.org/jira/browse/OLINGO-1541
Project: Olingo
Issue Type: Improvement
Components: odata4-samples
Affects Versions: (Java) V4 4.8.0
Reporter: Eugen Deutsch
We've a REST-Service and we are currently evaluating whether we should add
OData by using Olingo. The problem is that the examples
([https://olingo.apache.org/doc/odata4/index.html|https://olingo.apache.org/doc/odata4/index.html])
show how one needs to manually check for arguments, filter the objects, create
the entities and much more. Is this really the way to go?
{code:java}
final Entity e2 = new Entity()
.addProperty(new Property(null, "ID", ValueType.PRIMITIVE, 2))
.addProperty(new Property(null, "Name", ValueType.PRIMITIVE, "1UMTS PDA"))
.addProperty(new Property(null, "Description", ValueType.PRIMITIVE,
"Ultrafast 3G UMTS/HSDPA Pocket PC, supports GSM network"));
{code}
Is this really necessary? Spring takes the objects that are used in the
controllers and serializes and deserializes them into and from JSON using
Jackson. Can Olingo do something like this?
If yes: Create an example of how to do it. The current examples seem to be old.
If no: Why not? This should be added.
The JPA adapter for Olingo could somehow do it, but it only supports OData V2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
