Use Case Activator

Purpose

UseCaseActivator is the runtime component responsible for loading a requested use case on demand. It is registered by the bootstrapper and later used by BPUAApplication when a use case needs to be activated.

Main Responsibilities

• validate the activation request,
• resolve the physical folder for the requested use case,
• load the assemblies found in that folder through the existing dynamic assembly loading pipeline,
• stamp the registry so repeated activation requests can short-circuit cheaply,
• compute a default route for the activated use case.

Single-Flight Activation

The current implementation uses a concurrent dictionary of lazy tasks so that only one activation attempt for a normalized use-case key runs at a time. This is an important safeguard in multi-request scenarios.

Registry Stamping

Once activation succeeds, the activator stores a UseCaseActivationStamp in the registry. Subsequent activation requests can then detect that the use case is already active and avoid unnecessary loading.

Default Route Calculation

The default route is derived from the use case name or, in special cases, from the last segment of the breadcrumbs. This shows that the activator is not only a loader; it also produces a small amount of UI-facing convenience metadata.

Summary

UseCaseActivator gives the platform one of its most important runtime properties: business use cases can remain physically separate until they are actually needed.

Table of Content BPUA Chapter Previous: Dynamic Assembly Loading Next: Validation Subsystem

 

---

Business Process Programming in .Net
© 2004-2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness or suitability of the information and are not responsible for any damages resulting from its use.