odata-api | OData v4 Protocol on .NET Core | Networking library

by mocoding-software C# Version: v3.0.0-rc.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | odata-api Summary

odata-api is a C# library typically used in Networking applications. odata-api has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

OData v4 Protocol on .NET Core

Support

Quality

Security

License

Reuse

Support

odata-api has a low active ecosystem.

It has 2 star(s) with 1 fork(s). There are 2 watchers for this library.

It had no major release in the last 12 months.

odata-api has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of odata-api is v3.0.0-rc.2

Quality

odata-api has 0 bugs and 0 code smells.

Security

odata-api has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

odata-api code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

odata-api is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

odata-api releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of odata-api

Get all kandi verified functions for this library.

odata-api Key Features

No Key Features are available at this moment for odata-api.

odata-api Examples and Code Snippets

No Code Snippets are available at this moment for odata-api.

Community Discussions

Trending Discussions on odata-api

Odata .Net core v4 mvc routing not working

Getting NoSuchMethodError (DestinationAccessor) when launching Spring Boot project with generated Java VDM

Found class com.sap.cloud.sdk.cloudplatform.naming.JndiLookupFacade, but interface was expected

QUESTION

Odata .Net core v4 mvc routing not working

Asked 2020-Aug-12 at 08:06

When learning Odata, i've tried a test project with books and then tried making my own with a database connected. Both projects has edmx version 4 and is similar configured.

However, when calling my methods with parameters in the original project, it doesn't work, but it does in the Book example. etc. odata/v4/Resources(1) than the books(1). I can fetch data from Companies and resources controllers, but not from AccountController even it's similar setup method wised. It returns 404 not found. I can do the ?$select filtering on the resources controller, but not on the companiesController. Every other odata function works as it should. Changing to odataprefix and odataroute, every controller works, but then the method calling with parameters doesn't work.

I'm unaware of what i'm missing or what is giving me this issue and are now searching for help.

The guides i've been following and reading about is linked below. I'm aware that prefix routing is differently, but it should work like the book test to begin with:

Kind regards

Start.cs - My project - Github => original project

...

ANSWER

Answered 2020-Aug-12 at 08:06

The 404 when calling odata/v4/Accounts is because while your entity set is named Accounts your controller is named AccountCoutroller. Make it AccountsController and that will take care of the 404
With regard to the query options ($filter, $select, etc) working on /odata/v4/Resources but not working on /odata/v4/Companies, note that GetCompanies action returns CompanyResponse (and not Company) objects. CompanyResponse is not represented in the service metadata - it's not in the EDM. The response you're actually seeing is because your API is falling back on ASP.NET Web API serialization. OData will have a challenge constructing the $filter or $select expressions since it "knows" nothing about CompanyResponse. Returning Company objects would fix the issue.

Source https://stackoverflow.com/questions/63357670

QUESTION

Getting NoSuchMethodError (DestinationAccessor) when launching Spring Boot project with generated Java VDM

Asked 2020-Jul-31 at 13:16

I'm building a Spring Boot project making use of S/4HANA custom OData Service and Java VDM. I have been following various tutorials on SAP Blog, developer.sap.com or S4H13 course - the approach is pretty much the same. I managed to successfully generate VDM for my Custom OData Service based on the edmx file, created all necessary commands, methods in the controller and so on.

Unfortunately, I'm encountering an issue when launching the project locally. I use the following command first: mvn clean package and later, when I'm in the application directory want to run the project: mvn spring-boot:run.

The project build fails with the following errors and exceptions:

2020-07-31 12:45:20.941 ERROR 70176 --- [main] o.a.c.c.C.[Tomcat].[localhost].[/] : Exception sending context initialized event to listener instance of class [com.sap.cloud.sdk.s4hana.connectivity.ErpDestination]

...

ANSWER

Answered 2020-Jul-31 at 13:16

Please find the outdated dependency in your dependency tree:

Source https://stackoverflow.com/questions/63191113

QUESTION

Found class com.sap.cloud.sdk.cloudplatform.naming.JndiLookupFacade, but interface was expected

Asked 2020-Mar-25 at 13:55

I am getting the issue described up above when running integration tests.

The full error message follows:

...

ANSWER

Answered 2020-Mar-25 at 13:55

Looking at the dependency tree, I can see that there is a mix-up of SDK dependencies of version 2 and 3 in your project which is causing the issue.

The dependency entries with groupId starting with com.sap.cloud.s4hana are mostly v2 dependencies and the ones with groupId starting with com.sap.cloud.sdk are v3 dependencies.So, please use this as a reference to convert all v2 dependencies to the corresponding v3 dependencies.

Alternatively, you can also include the sdk-bom dependency (groupId: com.sap.cloud.sdk, artifactId: sdk-bom ) in your pom with a version, so that you can start including other sdk dependencies without explicitly including the version information. This would also ensure that all the sdk dependencies you include would always fall into the a particular version:

Source https://stackoverflow.com/questions/60818178

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install odata-api

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: