[
https://issues.apache.org/jira/browse/OLINGO-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruben van Diggelen updated OLINGO-1195:
---------------------------------------
Description:
*Given:* An OData API just after reboot.
*When:* The following query is carried out:
https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
2017-10-20T12:05:00+01:00
resulting in a normal process in the class implementing the
ExpressionVisitor<Object>
*Expected:* A query result
*Observing:*
{
"error": {
"code": null,
"message": "Cannot find type with name: OData.Lagerwey.LoggerType"
}
}
When we then go to the url https://localhost:8444/odata/v1/$metadata
all the metadata is correctly shown.
If we then visit the first url again
(https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
2017-10-20T12:05:00+01:00) all the data is return by the OData API.
We are able to solve this issue by calling
serviceMetadata.getEdm().getSchemas() in our Rest controller which exposes the
Odata instance to the web.
was:
*Given:* An OData API just after reboot.
*When:* The following query is carried out:
https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
2017-10-20T12:05:00+01:00
resulting in a normal process in the class implementing the
ExpressionVisitor<Object>
*Expected:* A query result
*Observing:*
??
{
"error": {
"code": null,
"message": "Cannot find type with name: OData.Lagerwey.LoggerType"
}
}
??
When we then go to the url https://localhost:8444/odata/v1/$metadata
all the metadata is correctly shown.
If we then visit the first url again
(https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
2017-10-20T12:05:00+01:00) all the data is return by the OData API.
We are able to solve this issue by calling
serviceMetadata.getEdm().getSchemas() in our Rest controller which exposes the
Odata instance to the web.
> Custom type cannot be found
> ---------------------------
>
> Key: OLINGO-1195
> URL: https://issues.apache.org/jira/browse/OLINGO-1195
> Project: Olingo
> Issue Type: Bug
> Components: odata2-core, odata4-server
> Affects Versions: (Java) V4 4.4.0
> Reporter: Ruben van Diggelen
> Priority: Minor
>
> *Given:* An OData API just after reboot.
> *When:* The following query is carried out:
> https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
> 2017-10-20T12:05:00+01:00
> resulting in a normal process in the class implementing the
> ExpressionVisitor<Object>
> *Expected:* A query result
> *Observing:*
> {
> "error": {
> "code": null,
> "message": "Cannot find type with name: OData.Lagerwey.LoggerType"
> }
> }
> When we then go to the url https://localhost:8444/odata/v1/$metadata
> all the metadata is correctly shown.
> If we then visit the first url again
> (https://localhost:8444/odata/v1/Logbook?$filter=DateTimeOffset ge
> 2017-10-20T12:05:00+01:00) all the data is return by the OData API.
> We are able to solve this issue by calling
> serviceMetadata.getEdm().getSchemas() in our Rest controller which exposes
> the Odata instance to the web.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
