Library support: mixed namespaces

[eparovyshnaya]

Library

A Passage User develops a library and protects it with Passage as a Library.

As library must take care of not demand satisfaction for foreign Licensing Requirements, it uses NamespaceConfiguration for, say, namespace com.company.smartidea.

This library is spreading among his clients and is successfully licensed.

Product

Then he builds a standalone product over the library, which itself is protected with Passage. Namespace of the becomes included into the one of the library. Like com.company.smartidea.standalone.

This product is licensed seaprately, and the licenses grants access only to this product's features and not for the library ones.

Here comes the sun

At the product runtime both product and library perform licensing coverage assessment.

Product rises only Requirements on its own scope. These requirements are addressed by valid product license.

But Library finds all requirements (including the product ones), as the library namespace is literally contains product's one.
All library requirements are addressed by proper library license, but the ones for product feature (not rightfully fetched and risen) cannot be covered.

Solutions

Following approaches look handy:

• evolve assessment engine to take more care of merging examination certificates from different sources (now they are just summed)
• make new configuration smart enought not to grab foreign requirements even if they are sub-namespaced.

Both are to be solved as parts of Cordon Runtime libs.