Thanks , I've already tried this approach but this time no hangfire jobs are registered. So for now I'll be waiting for the other issue solution I think. As a result of this topic , I understand that we shouldn't override a module if there isn't any problem, right ? Thank you.
Ok thank you, we'll be calling SetAsync() method before.
Actually I don't want to change options I want to change for example OnApplicationInitialization method behaviour because of an internal module error . I've also opened the issue related with this topic , you can check the specific case from below link :
https://support.abp.io/QA/Questions/2578/AbpBackgroundWorkersHangfireModule-exception-without-using-hangfire-configuration
But I'll try your module approach. Note => If the issue in the link above will be fixing , we don't even need to change the module.
Hello , Normally I shouldn't reach the entity repository like that from DDD manner , It's not a best practice. Because I should delete them from aggregate repository, so normally we don't have any repositories for entity itself. Anyway I've tried this approach , too. But it didn't work.
Hello all,
Is it possible to override one of the AbpModule itself ? There are lots of way inside the below link: https://docs.abp.io/en/abp/latest/Dependency-Injection#DependencyInterfaces But none of them are mentioning about overriding or replacing a module itself. For example I want to change AbpBackgroundWorkersModule module's ConfigureServices method inside, how can I do that ? Thank you.
Hello all,
NOTE => First of all we've found this usage by searching from your code, could you please share a usage of DynamicOptions inside your docs , too ?
The usage sample like below :
We have an optionsManager
Then an options class :
And the configuration is like below :
We are settings OdmsOptions inside SettingAppService like below :
When a person changes the options from setting page, we are just updating our options with Set() method call.
After that we want to get the latest options with injecting this Option class like below :
But after injecting this OdmsOptions class we are getting default options, not setted options. Why the behaviour is like that. We needed to call OdmsOptions.SetAsync(); method again to get latest settings, Why do we need another Set method call , we've already done this setting in another place. When we are injecting the Odmsoptions , should we get the latest changes without calling another set method ?
Could you check and help please? Thank you.
Hello all,
We're using hangfire background worker in our project we we're referenced this library in our dependent modules like below :
But this module has an issue , after that module is injected in our domain module , we are getting errors like below at irrelevant places like identity Server .
We've disabled the usage of backgroundworker and job inside of Identity Server Module :
But exception is still occurring. We've trace your code and we are thinking the base problem is in AbpHangfireModule
We're thinking this issue is occurring because of wrong ordered configuration .
You can see below your AbpBackgroundWorkersHangfireModule using AbpBackgroundWorkerOptions .
when we disable the AbpBackgroundWorkerOptions , it'll pass the exception but it'll continue with below module which is AbpHangfireModule.
So because of the OnApplicationInitialization method , even we don't have any job storage for example inside Identity Server module, we're getting below irrelevant exception.
Could you check the usage of this module. We are bypassing the problem like below in our project , we just wrapped exception with try catch and we don't do anything (override the AbpHangfireModule like below ):
So with this bypassing we can use IdentityServer and other related modules with hangfire module without exception.
Exception like below :
But we're thinking you should check this one.
Thank you.
Hello all,
We came up to an issue with abpContext and ef core.
We have an entity which is using ISoftDelete interface like below (and default behaviour is cascade delete with parent ).
And this entity is the child of parent Model aggregate root. We have a case like => we want to mark as deleted this entity and after we want to hard delete this entity from database without deleting parent Model entity. We are getting these children from db like below :
after that point we are operating deletion inside rich domain model like below (with removeall or clear it doesn't metter, it's not working):
So this operation should mark exports as deleted(in ef core state) and after saveChanges operation it should be deleting all exports from db. But nothing happened. (we also check with sql profiler , there wasn't any deletion operation which should be seen ). And as ef core state we also can't see the state change , children entity stayed as unchanged .
We've also checked this issue without abp library with just using ef core library. And with default ef core lib , we can get included children with parent, after that we marked these children with removeAll or clear methods and it worked as expected and this operation deleted all the children of the parent object without deleting parent. So we're thinking that this issue is related with abp framework library . Could you help with that issue , please ? It's really important for us.
Thank you.
Ok, thanks for the information.
Is this the abp design or it comes from Ef core ORM usage ? Because normally when you directly listen table changes from sql we can catch the changes. I understand that abp's pre-built events do not support this cascade deletion , right ?
