I am having troubles with updating my OData Client.
I would refer to How to call bound functions / actions inside Java client using SAP Cloud SDK? where people from SAP helped me alot, thanks!
Issue is, I wanted to update dependency to last version of SAP Cloud SDK because of new functionality that supports bounded functions and actions.
Back then (4 months ago), I had written myself documentation how to generate and use OData Java client properly, using SAP Cloud SDK. Quite a number of people was succesful back then with installing.
Now, 4 months later, I cannot generate properly client. I have installed lombok and also set it as reference in Eclipse and am using latest Eclipse (2021-06).
I will put screenshots of my errors. It says like my properties are not generated properly and that 1 method is missing - getOdataType().
These problems just started to occur last 2 weeks or so.
Thank you in advance!
Related
At the time of this post there are two Azure Service bus SDKs sitting within sdk/servicebus:
Microsoft.Azure.ServiceBus
Azure.Messaging.ServiceBus
They have both been updated very recently (past week).
This ms doc (written two weeks ago) states;
This quickstart uses the new Azure.Messaging.ServiceBus package. For a
quickstart that uses the old Microsoft.Azure.ServiceBus package, see ....
Where as this document (also written two weeks ago) says;
There are two supported Azure Service Bus .NET SDKs. Their APIs are
similar, and it can be confusing which one to choose. Refer to the
following table to help guide your decision. We suggest using the
Microsoft.Azure.ServiceBus SDK as It's more modern, performant, and is
cross-platform compatible. Additionally, it supports AMQP over
WebSockets and is part of the Azure .NET SDK collection of open-source
projects.
This document goes on to mention Microsoft.Azure.ServiceBus as newer and (yet another SDK) WindowsAzure.ServiceBus as older. It does not mention Azure.Messaging.ServiceBus at all.
Does anyone have any advice on which SDK should be used for a new .NET Core 5.0 project?
(I have already reviewed this question which has not helped)
For projects that have no dependency on the older packages, use Azure.Messaging.ServiceBus. For everything else, look at the dependencies. For example, Azure Functions cannot use the latest package today. It will likely be addressed in the future just not ATM. I wrote a blog post awhile ago about these 3 packages. May (or may not) help you with your question.
I am searching for a solution to build and publish the AWS Lex bot via .NET SDK or via any other API.
Any help will be appreciated.
I just recently developed a working Amazon Lex Chatbot using .NET SDK and one of the tools that helped a lot was the GitHub Repo that AWS maintains for C#. Do note that they use .NET core and not .NET framework.
Alternatively, if you want to use the REST API (which is what I did), you can go to the .NET documentation guide that Amazon also maintains. These REST API can be accessed via the Nuget package that you can get inside Visual Studio itself.
Comments for the v3 api was just released. We're using the .net client library and as far as I can tell the new comments changes are not included in the latest dlls. Does anyone know when the changes will be included in the libraries?
I'm just trying to figure out if it's worth creating my own wrapper or not. Thanks!
I just uploaded the new v3 version to NuGet.
I run the NuGet publisher once a week to update all Google.Apis packages. I already ran it this week, but with your request I just ran it again.
I am currently using Delphi 5 and planning to migrate application to latest version(XE3) or to other technology. Main purpose of migration is dont want thick client. In currrent scenario application(exe) gets downloaded to the users local folder and then it runs rom local. Main purpose is dont want to download the application to users machine. .
Wanted to stick with Delphi if that downloading limitation resolved. Is there web solution? or way to access the application from common point without downloading to users machine.
Thanks for the help and suggestions.
Note: There are lots of users who uses these application.
Depending on the type of application you could add web layer around the core functionality of your application.
If you create something like a SOAP or REST interface, you can write a web client in any language that suits. Could be Delphi, or some more web-oriented language like PHP or ASP.Net.
By having a web interface your users can access from any platform.
On the other hand, if your current application is not layered properly, and you've got a lot of code mixed between the GUI and your model, this could be difficult. It would mean rewriting a lot of code, or just accept the fact that your users need Windows, and an .exe file.
At least by using Delphi, your users don't need to download a huge framework that requires administrator privileges to install.
Anyway, you should provide some more information about what you already have, and what type of application it is, how complicated it is, etc.
If you are planning a move to Java Enterprise Edition (Java EE), accessing existing Delphi logic can be achieved using two communication models, using existing commercial and open source solutions:
for synchronous (request/response) style communication between Delphi and Java, there are lightweight web frameworks for Delphi (I wrote this one recently) and open source JSON/XML libraries which can be used for data exchange. This allows the Java application server to access Delphi logic over HTTP
for asynchronous communication, I wrote (commercial) message broker client libraries for Delphi and Free Pascal, they can be used with the Java Message Service (JMS) servers in the JBoss and the GlassFish application server - JBoss and GlassFish already include a messaging solution (HornetQ and Open MQ), as a mandatory part of the full Java EE profile
I also have written some step by step tutorials for JBoss and GlassFish Delphi integration:
Delphi Integration with JBoss Application Server 5
Delphi Integration with the GlassFish v3 Application Server Part 1 - Sending Messages
Delphi Integration with the GlassFish v3 Application Server Part 2 - Receiving Messages
Working on a Windows 8 (metro style) application, and want to reference a service hosted by ServiceStack from it. Since I cannot use the C# client objects provided by ServiceStack (can't reference the DLL from a Windows 8 project) I figured I'd have to fall back to adding a service reference using svcutil or from within VS 2012. When I do this, I get the following error:
Warning 5 Custom tool warning: Endpoint 'WSHttpBinding_ISyncReply' at address 'http://localhost/ServiceStackRD/soap12' is not compatible with Windows Store apps. Skipping... C:\Development\GridPresenter\GridPresenter\Service References\ServiceReference2\Reference.svcmap 1 1 GridPresenter
Does anybody know what makes an endpoint "not compatible with Windows Store apps?" If so, how do I tell ServiceStack to modify the endpoint definition to make it play nice with Windows 8 apps? Thank you.
SOAP and WSDLs are an ugly solution on any new platform, you have to get too many moving parts right for it to work properly.
The path of least resistance would be to use a C# HTTP Client that supports a Windows 8 Metro app and just parse the JSON returned from ServiceStack's JSON services. Here's an example of parsing GitHub's 3rd party API using these WebRequest extensions in ServiceStack.Text.
The community has yet to contribute a Windows 8/Metro App build of ServiceStack.Text so you will likely have to use another JSON serializer that does support it.