This is indeed a limitation of sharing a model JAR across two guvnor (5.5)
installations.
If duplicating the JAR in different guvnor installations is not an option;
then you need to look at using a single repository, adding the JAR to
"Global Area" and sharing into different packages.
One package could be equivalent to "base" and another to "custom".
You
should be able to restrict access to the packages by setting up the
appropriate security.
If your current "base" and "custom" installation contain many packages
then
the above line becomes more cumbersome.
6.0 doesn't have this limitation. You can upload the model JAR to a central
repository and import it into different projects.
With kind regards,
Mike
On 29 October 2013 10:27, Soumya.plavaga <soumya.bose(a)plavaga.in> wrote:
Thanks Mantis for the quick reply. I have updated my query.
We have a multi-tenant application. We need to maintain a common set of
base
rules that will be applicable to all our tenants and then We have few rules
that will be per tenant specific. For this, we have created two guvnor
repositories, one having a base set of rules with models and another having
custom rules. We will be having one repo of second type of repo per tenant.
But the problem with this approach is:
- if we have models in both the repo types, then there will be duplicates
when we import the repos into kbase.
- if we have models only in base repo, then we can not compile the rules
within custom type repos due to failed model dependency.
I would like to know, if this is the right approach or there is another way
to accomplish the same? We are using drools-guvnor version 5.5.Final.
--
View this message in context:
http://drools.46999.n3.nabble.com/Guvnor-5-5-0-Final-How-do-we-maintain-t...
Sent from the Drools: User forum mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users