|
We are deploying 2 applications which has a Class with the same canonical name (e.g. com.example.BusinessObject), we stored instances of this class to Business Repo, now every time I load the instances of BusinessObject, I see all instances from two different applications. Is there any way to limit Business Repo only load instances from the current applications? Is it a bug in Ivy Engine related to this? |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 22.01.2019 at 03:58
Seen: 1,274 times
Last updated: 07.08.2019 at 03:47
can you share the idea why you have duplicated that class? are you trying to implement a multi-tenancy approach with multiple apps? In my opinion a business data class should be very specific and bound to context of the actual project. So it seems strange to me to use the same class in separate projects...
I share the ideas of reguel. But at the end this is a bug. we use the same index for the same java class all over the engine. we should split this index further by application. i already did some research some times ago. but nothing is planned at the moment to fix this.
We have a core module which has the BusinessObject, then we have many other module provide functionality and reuse the BusinessObject from core module.
We have two branch of applications which have different set of functionality but depend on the same core module.
We deploy that two set of modules on two separate applications on the same Ivy Engine and face the issue.
We face the same problem with a customer who deploys the same application twice on the same engine and the data are not kept separated per application.
Is there any progress for this topic or do you have a tip to find a quick working solution?
Hello Fotini As I have learned, this is not a bug but a conscious design decision. But the spirits are divided whether this is good or not. For you at the moment, the only solution is to model the name of the app itself in the business data and to consider the name of the app in queries. There is story to tackle this XIVY-3063, but not planned. Push this story at your stakeholder responsible.