Activities of "Neozzz"

I dont want to use admin and saas in mongo. I want to use it as sql as they're part of the main microservice sln called 'ZW' which uses efcore. My microservice "CompanyService" service should use mongo only for crud on the entities in that.

As explained in the first post:

ZW - name of main microservice solution uses angular and efcore ZW.CompanyService - name of the microservice service project which uses angular and mongo.

Hi I added the MongoDB project and removed the EntityFameworkCore project. I am still facing the same problem. It looks like when I add mongo reference its trying to use everything associated with the project like saas and admin to work with mongo. I only want to use mongo for CRUD purposes of an entity.

Please help Tx.

Hi issue is resolved. I had added a file management service to the main solution.

abp new FileMgmt -t microservice-service-pro cd services/FileMgmt/...Application abp add-module Volo.FileManagement dotnet add package Volo.Abp.BlobStoring.Database.MongoDB --version 4.3.0

Turns out I have to add license to this project as well even though am only running the SubProject that doesn't require any commercial module.

the newly created microservice service solution.

updated 28th,apr.

please update.

Answer

Hi, Thanks! That fixed the issue. We added reference to administrationservice and inside the administrationservicemoduleas you said. But even though it showed the service entity under permissions for a brief moment, it is giving "500 Internal Server error" when I try to login after logging off to the web app at 44321 port number.

This is the url: https://localhost:44322/Account/Error?errorId=CfDJ8B_truncated

But at the web page at this address it shows as the user is logged in though.

Any guess why this might be happening?

Thank you :)

Answer

Hi Alper,

I took a look at the product-service example. And that hasn't referenced application.contracts and it still shows under the permissions page.

While trying to POST an entity "organization" to a module solution, it is not accepting saying that the name field is not available. Also I had implemented a separate controller in the HttpApi project for handling requests, but looks like it is not being used. Would like to know why the name field is not being shown on swagger POST request section also should we init when doing a separate controller?

Because it has private setter.

We're alos improving the microservice solution that I highly recommend you to check microservice template docs if you haven't already.

Also please make your repository private, commercial applications shouldn't be host in public repositories.

Hi Thank you for the reply. That worked. Thanks !

I had created a controller inside the httpApi project as well. But it looks like the end point is still handled by the framework itself. How can we configure the framework to use the new controller?

Thank you

I couldn't find a proper solution from that link. It looks like changes made to code in previous versions. The current version should have it already I suppose? If so, what might be the fix?

Thanks

Showing 101 to 108 of 108 entries
Made with ❤️ on ABP v8.2.0-preview Updated on March 25, 2024, 15:11