[
https://issues.apache.org/jira/browse/OLINGO-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646050#comment-14646050
]
Christian Amend commented on OLINGO-742:
----------------------------------------
Hi Ramesh,
but then how would you keep apart simple names from fully qualified names? The
current logic we use inside the library always uses the last period it finds to
split a namespace from a name.
In the URI case encoding would not work as you have to decode before
interpreting a segment. Maybe replacing every period with a dash would work in
your case although this is cumbersome.
BTW: we had a name validation inside the EDM in V2. In V4 we did not implement
a name validation as we said this would take too much performance when building
a "Named" Edm element. Should we introduce this in the EDM again so developers
don`t define invalid metadata and then think the issue lies with serialization
or URI parsing, WDYT?
Best Regards,
Christian
> EntitySet name does not allow period "." in its name
> ----------------------------------------------------
>
> Key: OLINGO-742
> URL: https://issues.apache.org/jira/browse/OLINGO-742
> Project: Olingo
> Issue Type: Bug
> Components: odata4-server
> Affects Versions: (Java) V4 4.0.0-beta-01
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.0.0
>
>
> If the EntitySet name is like "public.g1", the parser does not allow the GET
> request like
> {code}
> GET /svc/public.g1
> {code}
> it fails with "'g1' is only allowed for typed parts", any type EntitySet
> name should be allowed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
